Copyright © Cloud Software Group, Inc. All Rights Reserved

Prerequisites for the CA Datacom Environment

You must complete the following tasks for your CA Datacom environment before you can access the CA Datacom data:

•	Generate the CA Datacom User Requirements Tables.

•	Optionally, populate the Data Dictionary tables.

•	Define the CA Datacom environment.

For details, see the following sections.

Generating the CA Datacom User Requirements Table

The server can use multiple URTs to access your data. Those URTs are loaded at runtime and must, therefore, reside in one of the load libraries available to the server. You must ensure that any URTs that you provide have DBNTRY as the main entry point.

Populating Data Dictionary Tables

Before defining the CA Datacom environment, you might want to extract some metadata from the CA Data Dictionary into TIBCO Object Service Broker. Use the DATACOM interactive tool to extract the metadata of your choice.

Also, you can run the extraction as a separate job. Member DCOMDEXT in the JCL data set contains the JCL for extracting metadata from CA Datacom Data Dictionary tables into TIBCO Object Service Broker.

The interactive DATACOM tool can be used for extracting metadata from CA Datacom Data Dictionary only if your TIBCO Object Service Broker runs on z/OS. In other cases (Windows or Solaris), your only choice is running the DCOMDEXT JCL as a separate job on z/OS with the TDS parameter denoting your TIBCO Object Service Broker.

Defining the CA Datacom Environment

The CA Datacom Master List and the URT must be properly defined before the server can run.

Defining the Master List

The following parameter must be set to control the CA Datacom environment:

TASKS

Specifies the maximum number of tasks that can operate concurrently within CA Datacom. Each server that is running uses one task.

Defining the User Requirement Table

Set the following parameters for the URT:

Parameter	Macro	Description
OPEN=USER	DBURINF	Indicates that the server is responsible for the open and close processing of the URT.
URTABLE=ASM	DBURINF	Indicates that the CA Datacom macros are assembled as one object when the URT is generated.
TIMEMIN=0, TIMESEC=1	DBURSTR	Indicates that control is to be returned to the caller immediately upon a failed attempt to lock a row. This behavior is essential for the TIBCO Object Service Broker DAT Server’s ability to signal the LOCKFAIL exception when appropriate; the CA Datacom default behavior is a “wait forever” condition.
TXNUNDO=YES	DBURSTR	Indicates that all tables described in this URT use logging when modified (see UPDATE=YES), so TIBCO Object Service Broker's ROLLBACK statement can be carried out against tables of type DAT mapped to them (CA Datacom will commit data if TXNUNDO=YES is not specified).
UPDATE=YES	DBURTBL	Indicates that the caller can modify the rows in this table. Also, callers that issue CA Datacom’s SELxx commands (TIBCO Object Service Broker DAT Server falls into this category) require UPDATE=YES. See the CA Datacom documentation for details.

Your URT must have DBNTRY as the primary entry point (use the linkage editor's ENTRY DBNTRY control statement). Also, you can provide multiple URTs. For details, see Adding URT Names.

Copyright © Cloud Software Group, Inc. All Rights Reserved