The Batch Interface › SYSIN01 Parameters › Coding XTC Transfers in an XCOMPLEX Environment

Coding XTC Transfers in an XCOMPLEX Environment

When submitted to the Admin server or PLEXQ group, all XTC transfers within a SYSIN01 input are routed and scheduled to the same server. This server is selected for the first XTC transfer in this group.

TYPE=SCHEDULE XTC transfers submitted through the XCOMPLEX Admin or PLEXQ Group must have XTCJOB and XTCNET names that are unique to the submitted XCOMJOB.

Note: Use an individuals z/OS TSO signon ID as the XTCNET name to make sure that it is unique.

All transfers within each SYSIN01 are executed, released, or purged, and cannot be extended into subsequent SYSIN01s. The transfers cannot be extended because new transfers may be scheduled by the Admin to a server other than the one chosen for the initial SYSIN01.

When using XTC to submit multiple jobs or job steps with the same XTCNET and XTCJOB names, submit directly to the CA XCOM server. Submitting directly ensures that they go to the same CA XCOM Server.

At the end of each XTC run, ensure that there are no XTC transfers left in HOLD status. Use the CA XCOM Data Transport DELETE or RELEASE operator commands to do this. For more information, see the chapter Operation and Control.

Note: Go into the appropriate servers and use the CA XCOM Data Transport SHOW command to check for any left over XTC transfers before resubmitting an XTC transfer job. Use this procedure to clean up any transfers in HOLD status.