XMIT JCL statement

Support for the XMIT JCL statement:

The XMIT JCL statement has no function in an APPC scheduling environment. If you code XMIT, the system will check it for syntax and ignore it.
The XMIT JCL statement is supported on both JES2 and JES3 systems. In JES2 systems, however, the SUBCHARS operand is not supported.

Purpose: Use the XMIT JCL statement to transmit records from an MVS™ node to a JES3 node, a JES2 node, a VSE/POWER node, a VM/RSCS node, or an AS/400® node.

The sending system does not process or check the records for validity except when the JCL is processed by an internal reader (such as with TSO/E submit processing). In this case, the system recognizes /*EOF and /*DEL as internal reader control statements and errors can occur on the sending system if /*EOF or /*DEL are included in the XMIT JCL stream.

To transmit /*EOF and /*DEL statements as part of the XMIT JCL stream on a JES3 node, replace /* with two substitute characters and identify the substitute characters on the SUBCHARS parameter. Prior to transmission, the sending system converts the two substitute characters to /*. The receiving (execution) system can then process the /*EOF and /*DEL statements as internal reader control statements.

Note: Since JES2 does not support the SUBCHARS parameter, it also does not support sending /*EOF and /*DEL as part of the XMIT JCL stream.

Do not nest XMIT JCL statements. That is, do not include an XMIT JCL statement between an XMIT JCL statement and its delimiter.

The system builds network job header and trailer records from information on the JOB statement and any //*NETACCT statements, if included, preceding the XMIT JCL statement. Then the system transmits all the records between the XMIT JCL statement and a delimiter statement.

The records can consist of a job input stream, an in-stream DD * or DD DATA data set, or any job definition statements recognized by the destination node. If the records are a job input stream, and the destination node can process the JCL, the transmitted input stream is executed at the destination node. The records must be 80 characters long.

The records end when the system finds one of the following delimiters:

/* in the input stream, if a DLM parameter is not coded on this XMIT JCL statement. (Refer to the Delimiter Statement information for an explanation of /*.)
From TSO/E only, TSO/E inserts /* at the end-of-file if the default delimiter is not supplied.
The two-character delimiter specified by a DLM parameter on this XMIT JCL statement.