Previous Topic: Non-Swappable

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

Configuring and Customizing Your Product › Define the Server in a Standalone Environment › Operating Your Product

Operating Your Product

CA XCOM Data Transport operation can be initiated from the z/OS console by issuing the START command. CA XCOM Data Transport can also be submitted as a TSO or batch job. We recommend operating CA XCOM Data Transport as a server (that is, by using the START command at the z/OS console).

For a complete list of CA XCOM Data Transport operator commands, see the chapter “Operation and Control” in the CA XCOM Data Transport for z/OS User Guide.

Create a PLEXQ Environment (Optional)

CA XCOM Data Transport for z/OS can distribute and manage locally initiated transfers among servers in a CA XCOM Data Transport PLEXQ. A PLEXQ consists of one or more CA XCOM servers. Transfers intended for servers in the PLEXQ may be generically scheduled to the group name used by the PLEXQ server(s) as defined via the PLEXQ parameter.

Through the use of the IBM Parallel Sysplex Signaling Services, CA XCOM Data Transport manages the distribution of transfer workload amongst servers which are members of the same PLEXQ.

To create a PLEXQ environment, simply specify the same name in the PLEXQ parameter either in the CONFIG member or as part of the EXEC PARM for each CA XCOM server which is to participate in the same PLEXQ.

Multiple PLEXQ environments may be defined within a SYSPLEX, however, a server may participate in only ONE PLEXQ group at any given time.

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

Define the PLEXQ Server(s) (Optional)

To make a CA XCOM Data Transport server a member of a PLEXQ (see Define the CA XCOM Data Transport Server in a Standalone Environment in this chapter) configure it as follows:

To define a Server as a member of a PLEXQ

  1. Specify the name of the PLEXQ group using the PLEXQ parameter or by specifying it in the EXEC PARM for the server JCL.
  2. At least one PLEXQ server must be available in the PLEXQ or it will not be possible to schedule work to the PLEXQ.
  3. Each PLEXQ server must have its own XCOMRRDS and history file, and be configured to run as a standalone server.

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

Schedule Transfers to the PLEXQ

Transfers can be scheduled either to the PLEXQ group or directly to a server using the SNA or TCP/IP protocol. Transfers are scheduled to a PLEXQ by using the STCPLEXQ parameter in the EXEC PARM of the XCOMJOB utility program. Connections established to a PLEXQ do not use SNA or TCP/IP protocols, but rather a proprietary messaging protocol which uses SYSPLEX Signaling Services as its transport layer.

Attempts to schedule or inquire on transfers to a PLEXQ when no servers are active in the PLEXQ will be rejected.

Same Release

All servers which are members of the same PLEXQ group must be at the same CA XCOM Data Transport release.

Default Options

Parameters for transfers scheduled to a PLEXQ group member server can be taken from the Default Options for the server which ultimately receives the transfer request or from another specified Default Options configuration. Parameters specified in the SYSIN01 and destination members will override these parameters.

Sample PARM Statements

The following is a sample PARM statement. If it is used when sending transfers to a PLEXQ group member server, then CA XCOM Data Transport will take defaults from XCPTDFB0, which is a Default Options CONFIG member (or Table) for the target PLEXQ group server.

PARM=('TYPE=SCHEDULE,DFLTAB=XCPTDFB0,STCPLEXQ=PRODXCOM')