The input service processor also processes the /*XEQ control statement, /*ROUTE XEQ control statement, and /*XMIT control statement. JES2 converts the execution node specified in any of these control statements to a node number or specified userid, replacing the default (or previously specified) node number.

You can send jobs for execution on a guest virtual machine on a VM node by specifying a symbolic destination defined on a JES2 DESTID(jxxxxxxx) initialization statement. If you do not specify a symbolic destination, JES2 processing moves the second-level route code from the /*XEQ or /*XMIT JECL statement. VM uses the execution userid as the destination virtual machine for the jobs it receives.

If the execution node number does not match the input node, JES2 will not process any execution-related control statements. JES2 processes JES2 control statements on the input node and the execution node when they appear before the /*XEQ (or /*ROUTE XEQ) control statements. If you place the /*XEQ (or /*ROUTE XEQ) statement before other JES2 control statements, JES2 processes only the/*MESSAGE and /*SETUP control statements at the input node if they come before the /*XEQ statement. All other control statements are not processed until they reach the execution node.

Use the /*XMIT control statement to submit data into the network. The transmitter considers all data following an /*XMIT statement, up to a delimiter statement as one network job. The delimiter statement defaults to /*, but can be changed through the DLM= parameter on the /*XMIT JES2 control language statement. For information about specifying this delimiter, see the z/OS MVS JCL User's Guide. The network job is transparent to all nodes but the receiving node.