Execution at remote node (non-APPC)

JES control statements and the XMIT statement have no function in an APPC scheduling environment.

You can enter a job through your system to execute on another system by coding one of the following statements. The job can be entered through an input reader, an internal reader, a TSO/E terminal, or an RJE (remote job entry) or RJP (remote job processing) terminal or work station.

When Entered through a JES2 System:

And received by a JES2 system, code one of the following:

   //name  XMIT  DEST=node,DLM=xx
   /*ROUTE XEQ node  
   /*XEQ node

And received by a JES2 system or a JES3 system, code:

   //name  XMIT  DEST=node,DLM=xx
   /*XMIT node

And received by a VM system with an MVS™ system running as a guest, code one of the following:

   //name  XMIT  DEST=node,DLM=xx
   /*ROUTE XEQ node.vmguestid  
   /*XEQ node.vmguestid  
   /*XMIT node.vmguestid

When Entered through a JES2 or JES3 System:

And received by a system other than a VM system, code: <
```
    //name  XMIT  DEST=node,DLM=xx  
```
And received by a VM system with another system running as a guest, code:
```
    //name  XMIT  DEST=node.vmuserid,DLM=xx  
```

Use of XMIT JCL statement with a JES system

When writing new JCL, IBM® recomends using the XMIT JCL (//name XMIT form) since this statement is not dependent on using a particular JES subsystem (provided you do not need to use the SUBCHARS= operand, which is not supported by JES2). In addition, the XMIT JCL is prefered because it allow transmission of records that a //*ROUTE XEQ, /*ROUTE XEQ or a /*XEQ statement does not allow.

For example, a JOB statement for the receiving node must immediately follow a //*ROUTE XEQ statement. This requirement means that a //*ROUTE XEQ statement cannot be used to transmit records beginning with $$ POWER® control statements to a VSE node; however, an XMIT JCL statement can transmit such records.