Configuring and Customizing Your Product › Define the XCOMPLEX in a Coupling Facility Environment (Optional, Deprecated)

Define the XCOMPLEX in a Coupling Facility Environment (Optional, Deprecated)

Important: The existing XCOMPLEX facility has been deprecated. The following information is provided for backward compatibility only. All new installations use the new PLEXQ implementation. Existing XCOMPLEX users migrate to the PLEXQ infrastructure for their XCOMPLEX functionality.

CA XCOM Data Transport for z/OS can distribute and manage locally initiated transfers among XCOMPLEX Worker Servers in an XCOMPLEX. An XCOMPLEX consists of an Admin Server and one or more XCOMPLEX Worker Servers. All transfers for servers in the XCOMPLEX are scheduled to the XCOMPLEX Admin Server. The XCOMPLEX Admin Server does not actually perform transfers.

By using the IBM Parallel Sysplex Coupling Facility, various CA XCOM Data Transport lists are maintained to aid in the distribution of the workload.

To define the XCOMPLEX.

1. Define the overall IBM Coupling Facility data set. CAI.CBXGJCL(XCPF) contains a sample job to define the IBM Coupling Facility data set. This step is not needed if you have an existing IBM Coupling Facility defined.
2. Define a policy data set for the XCOMPLEX. This policy data set defines the XCOMPLEX to the IBM Coupling Facility. CAI.CBXGJCL(POLCFRM) contains a sample job to define XCOMPLEX structures to the Coupling Facility. An XCOMPLEX name can be one to 16 alphanumeric characters. The name for the XCOMPLEX must be unique and must not be the same as the acbname for any server in the XCOMPLEX. Servers are in a common XCOMPLEX, as long as they share a common Coupling Facility. There can be a maximum of 61 XCOMPLEX Worker Servers for each XCOMPLEX. For more information about working with the Coupling Facility, see the IBM documentation.

   Note: Multiple XCOMPLEXes can be defined, even on the same system.

3. Define which servers make up the XCOMPLEX. The name of the XCOMPLEX is specified in the Default Options Table using the XCOMPLEX parameter. All servers in the XCOMPLEX are identified by specifying the same name for the XCOMPLEX parameter in their respective Default Options Tables. Each server can belong to only one XCOMPLEX.

NOTE: All participant members of the XCOMPLEX must be the same release.