The Batch Interface › SYSIN01 Parameters › Coding Interdependent Transfers

Coding Interdependent Transfers

This section explains how to code a set of interdependent transfers in the SYSIN01 DD statement.

• The SYSIN01 parameter NEWXFER is used at the beginning of each of the multiple transfer requests as shown in the following diagram:

  JOBNAME . . .                              
                                                        
  //STEP1. . . PGM=XCOM,PARM=('parm=parm_value')
  	.
  	.
  	.
  //SYSIN01 DD *                                        
                                                        
                                                        
                                                        
  transfer request 1 parameters
                                                        
                                                        
  NEWXFER                                               
                                                        
                                                        
  XCOMJOB                                               
  JCL                                                   
                                                        
  SYSIN01                                               
                                                        
  transfer request 2 parameters
   The NEWXFER parameter is used
   in the SYSIN01 DD statement
   to signal the beginning of 
   each new transfer request  1,2,...i.
  
  NEWXFER                                               
                                                        
                                                        
                                                        
                                                        
  transfer request i parameters
                                                        
                                                        
                                                        
                                                        
  /*                                                    
                                                        
  //                                                    
  

• The parameter XTCNET is used to indicate which transfer requests belong to the same group (are dependent on each other). Suppose, for example, that the transfers XFER1, XFER2 and XFER3 are grouped together. Accomplished this by simply assigning the name of the group (say, GROUP1) to XTCNET and including XTCNET=GROUP1 in the definition of each of the three transfer requests. If XTC transfers are requested using the XCOMPLEX, the XCOMPLEX Admin Server distributes all transfers with the same value for XTCNET to the same XCOMPLEX Worker Server. If XTC transfers are requested using the PLEXQ, all transfers with the same value for XTCNET are distributed to the same server within the PLEXQ group.
• Each interdependent transfer request must have a unique name, which is assigned to the XTCJOB parameter. Thus, if XFER1, XFER2 and XFER3 are the names of three interdependent transfer requests, their definitions in SYSIN01 must contain the parameter XTCJOB=XFER1, XTCJOB=XFER2, and XTCJOB=XFER3, respectively.
• XTC parameters other than XTCNET and XTCJOB are used to indicate the dependencies obtaining between the transfer requests. The outcome of a transfer request can affect as many as eight other transfer requests. In addition to the XTC parameters, other SYSIN01 parameters can (and some, for example, the local file name or LFILE, must) be used when defining interdependent transfer requests.
• HOLD=YES must be coded in each transfer request that is dependent on the successful/unsuccessful completion of another transfer request. However, HOLD=YES need not be coded if the holding/releasing of the transfer request is controlled by the HOLDCOUNT parameter - shown following.

Example

The following sample definition contains three interdependent transfer requests:

//SYSIN01 DD *
NEWXFER                               /*Transfer request 1 follows*/
TYPE=SEND
FILE=A.B.C
LFILE=MY.FILE1
XTCNET=METS
XTCJOB=PAYROLL
HOLD=YES
NEWXFER                               /*Transfer request 2 follows*/
TYPE=RECEIVE
FILE=YOUR.FILE
LFILE=MY.FILE2
XTCNET=METS
XTCJOB=PAYME
HOLD=YES
NEWXFER                               /*Transfer request 3 follows*/
TYPE=SEND
FILE=PC.FILE
LFILE=MY.PC.FILE1
XTCNET=METS
XTCJOB=GETDATA
XTCGOODREL=PAYROLL
XTCGOODPURGE=PAYME
XTCERRPURGE=PAYROLL
XTCERRREL=PAYME
/*
//

In this example, the three transfer requests are identified as GETDATA, PAYME, and PAYROLL, and they belong to the group METS. Of these, GETDATA is the parent transfer request, that is, the request that tries to execute first and the execution of which controls the subsequent execution of the other two (dependent) transfer requests. Four XTC parameters (other than XTCNET and XTCJOB) are associated with the transfer request GETDATA. XTCGOODREL=PAYROLL means that the PAYROLL transfer belonging to the same group (METS) as GETDATA is to start if GETDATA completes successfully.

At the same time, the PAYME transfer is to be purged from the transfer request queue (XTCGOODPURGE=PAYME). However, if GETDATA does not complete successfully, then the PAYROLL transfer is to be purged (XTCERRPURGE=PAYROLL) and the PAYME transfer is to start (XTCERRREL=PAYME).

Note:TYPE=SCHEDULE is required for XTC transfer requests.