Configuring and Customizing Your Product › Configure the Default Options › Edit the Sample TYPE=CONFIG Member

Edit the Sample TYPE=CONFIG Member

CA XCOM Data Transport assigns default values for each TYPE=CONFIG member parameter. CA XCOM Data Transport takes these values for any parameter not specified or overwritten at installation time. However, in most cases, some level of customization is required to run CA XCOM Data Transport successfully.

The data set CAI.CBXGPARM (XCOMCNFG) on the distribution media provides a sample CA XCOM Data Transport TYPE=CONFIG member. For a printed sample of the dataset, see the Sample XCOMCNFG file in the appendix Sample Files in the CA XCOM Data Transport for z/OS User Guide.

You can edit the TYPE=CONFIG member to customize CA XCOM Data Transport to the requirements of your installation.

To edit the TYPE=CONFIG member

1. Copy the contents of data set CAI.CBXGPARM (XCOMCNFG), that contains the sample CA XCOM Data Transport TYPE=CONFIG member.
2. Open the newly created copy of the CA XCOM Data Transport TYPE=CONFIG member with a text editor of your choice.
3. Assign each of the parameters your installation default value.
4. Save the updated TYPE=CONFIG member.

Note: The TYPE=CONFIG member parameters are described in the chapter, Configuration Parameters.

Before the changes made to the TYPE=CONFIG member take effect, stop and restart CA XCOM Data Transport.

Specify the TYPE=CONFIG Member

Specify the name of the TYPE=CONFIG member using the CONFIG parameter on the EXEC card in the JCL initiating the CA XCOM Data Transport server or batch utility.

CONFIG=member_name

A TYPE=CONFIG member, that contains the initialization parameters and their respective value assignments that are implemented for the current CA XCOM Data Transport execution.

If you want to specify different environments for use with CA XCOM Data Transport, you can create a TYPE=CONFIG member for each environment. To enable a particular environment-specific TYPE=CONFIG member, specify its name as the value of the CONFIG parameter.

If no TYPE=CONFIG member name is assigned to the CONFIG parameter, CA XCOM Data Transport reads the default member matching the value of the DFLTAB parameter. If the DFLTAB parameter is also missing, CA XCOM Data Transport uses XCOMDFLT as the CONFIG member name for the parameter values.

Where to Store TYPE=CONFIG Members

The TYPE=CONFIG members can be stored in either a PDS data set specified in the XCOMCNTL DD concatenation or a PDS data set specified by the CONFIGDSN symbol.

Advantages of storing the TYPE=CONFIG members in a PDS data set specified in the XCOMCNTL DD:

• If your existing CA XCOM Data Transport procedures already include an XCOMCNTL DD concatenation, TYPE=CONFIG members can easily be added to one of the data sets in the concatenation without having to update the CA XCOM Data Transport procedure.
• The end users can easily add or update the XCOMCNTL DD concatenation to use a customized TYPE=CONFIG member.

Advantages of storing the TYPE=CONFIG members in a PDS data set specified in the CONFIGDSN symbol:

• If your existing CA XCOM Data Transport procedures do not already include an XCOMCNTL DD concatenation, the CONFIGDSN data set defines where to search for the TYPE=CONFIG member without having to update the CA XCOM Data Transport procedure.
• CONFIGDSN is set at the system level and cannot be overridden in the CA XCOM Data Transport procedure.
• The CONFIGDSN data set can also include a member name to enforce the use of a specific TYPE=CONFIG member.

Set CONFIGDSN

The CONFIGDSN symbol controls the search order CA XCOM Data Transport uses to load the TYPE=CONFIG member. The CONFIGDSN symbol is set at the system level and must be set using the CA XCOM Data Transport CAIRIM Initialization program (FXC0INIT).

The data set CAI. CBXGSAMP (FXC0RIM) on the distribution media provides sample CAIRIM initialization parameters to set or delete the CONFIGDSN symbol.

CONFIGDSN can be specified as:

• dsname – Load the TYPE=CONFIG member from the specified dsname.
• dsname(config) – Load the TYPE=CONFIG member config from the specified dsname.
• XCOMCNTL – Load the TYPE=CONFIG member from the XCOMCNTL DD concatenation.
• xxxxxx:XCOMCNTL – Load the TYPE=CONFIG member from the dsname or dsname(config) specified by xxxxxx. If not found, then load the TYPE=CONFIG member from the XCOMCNTL DD concatenation.

Note:

• The default for the CONFIGDSN symbol is XCOMCNTL.
• XCOMXFER and XCOMXADM ignore the CONFIGDSN symbol and can always load the TYPE=CONFIG member from the XCOMCNTL DD concatenation.

How the TYPE=CONFIG Member is Loaded

When CONFIGDSN=dsname, the TYPE=CONFIG member is loaded as follows:

• CA XCOM Data Transport searches the specified dsname to find the TYPE=CONFIG member. If found, the default options are read from the TYPE=CONFIG member.

When CONFIGDSN=dsname(config), the TYPE=CONFIG member is loaded as follows:

• CA XCOM Data Transport searches the specified dsname to find the TYPE=CONFIG member config, If found, the default options are read from the TYPE=CONFIG member.

When CONFIGDSN=XCOMCNTL or CONFIGDSN defaults to XCOMCNTL, the TYPE=CONFIG member is loaded as follows:

• CA XCOM Data Transport searches the XCOMCNTL DD concatenation to find the TYPE=CONFIG member. If found, the default options are read from the TYPE=CONFIG member.

When CONFIGDSN=dsname:XCOMCNTL, the TYPE=CONFIG member is loaded as follows:

• CA XCOM Data Transport searches the specified dsname to find the TYPE=CONFIG member. If found, the default options are read from the TYPE=CONFIG member.
• CA XCOM Data Transport searches the XCOMCNTL DD concatenation to find the TYPE=CONFIG member. If found, the default options are read from the TYPE=CONFIG member.

When CONFIGDSN=dsname(config):XCOMCNTL, the TYPE=CONFIG member is loaded as follows:

• CA XCOM Data Transport searches the specified dsname to find the TYPE=CONFIG member config, If found, the default options are read from the TYPE=CONFIG member.
• CA XCOM Data Transport searches the XCOMCNTL DD concatenation to find the TYPE=CONFIG member. If found, the default options are read from the TYPE=CONFIG member.

Note: XCOMXFER and XCOMXADM ignore the CONFIGDSN symbol and always loads the TYPE=CONFIG member from the XCOMCNTL DD concatenation.