Configuring and Customizing Your Product › Parameter Override Relations › Resolve Multiple Interpretable Parameters

Resolve Multiple Interpretable Parameters

CA XCOM Data Transport employs a special parameter evaluation hierarchy to resolve parameters with multiple interpretations to their correct values. The order in which CA XCOM Data Transport processes the various CA XCOM Data Transport parameter categories is as follows (1 = highest priority, 4 = lowest priority):

1. SYSIN01 parameters
2. CA XCOM Data Transport control library parameters
3. PARM field parameters in the EXEC statement invoking XCOMJOB or XCOMXFER
4. Default Options Table parameters or CONFIG member parameters

Create the New TYPE=CONFIG Member

CA XCOM Data Transport has a set of system parameters that govern its operation across all of its various interfaces. The CA XCOM Data Transport system parameters take effect as soon as CA XCOM Data Transport is started and, unless overridden, they remain in effect as long as CA XCOM Data Transport is active. These system parameters are kept in the CA XCOM Data Transport TYPE=CONFIG member.

For installations converting from a previous release, any existing, customized Default Options Tables can be assembled and linked using the #DFLTAB macro. The #DFLTAB macro is located in the CBXGMAC library that is provided as part of the CA XCOM r11.6 installation. A TYPE=CONFIG member is created the first time a Default Options Table is used to invoke CA XCOM r11.6 address space (XCOMJOB, XCOMXFER, or XCOMXADM). The created TYPE=CONFIG member has the same global parameter options specified in the Default Options Table. The TYPE=CONFIG member is created in the FIRST PDS data set that is allocated to the XCOMCNTL DD statement. The TYPE=CONFIG member maintains the same name as the Default Option Table it was created from.

NOTE: If you do not want CA XCOM to make any updates in your current XCOMCNTL data sets, allocate a new data set and place it first in the XCOMCNTL DD concatenation. Once a TYPE=CONFIG member has been created, it is used for subsequent executions. Changes to configuration parameters and defaults are maintained there, and the Default Options Table is no longer used.

If the Default Options Table is not assembled with the current version of the #DFLTAB macro, the server, or batch job, invocation terminates with messages similar to the following messages:

XCOMM002II DEFAULT OPTIONS TABLE SHOULD BE REASSEMBLED.
GEN-LEVEL/VERSION (xxxx-xxx) DOES NOT MATCH XCOMXFER (yyyy-yyy).

Note: For descriptions of CA XCOM Data Transport system parameters, see the chapter Configuration Parameters.