If the sending node is JES3, the system
holds the output data set at that node on the BDT queue (when transmitting
to an SNA-attached node) or the WTR queue (when transmitting to a
BSC-attached node) if all of the following are true:
- The "// DD SYSOUT=" JCL statement does not contain a DEST=(node,userid)
parameter.
- The SYSOUT= parameter does not contain the WRITER-NAME subparameter
and the output class is not defined as a hold class.
- No WRITER= parameter is coded on the OUTPUT JCL statement.
Example 1.
The following job executes
on NODE1 and results in the SYSUT2 output data set being held on the
BDT queue on NODE1. (NODE5 is attached to NODE1 via SNA and output
class A is not defined as a hold class.)
//S1 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=A
//SYSIN DD DUMMY
//SYSUT1 DD DSN=SYS1.PROCLIB(JES3),DISP=SHR
//SYSUT2 DD SYSOUT=A,HOLD=YES,DEST=NODES
Example
2.
The following job executes on NODE1 and results in the SYSUT2
output data set being held on the WTR queue on NODE1. (NODE5 is attached
to NODE1 via BSC and output class A is not defined as a hold class.)
//S1 EXEC PGM=IEBGENER
//O1 OUTPUT CLASS=A,DEST=NODE2.MYWRITR
//SYSPRINT DD SYSOUT=A
//SYSIN DD DUMMY
//SYSUT1 DD DSN=SYS1.PROCLIB(JES3),DISP=SHR
//SYSUT2 DD SYSOUT=(,),HOLD=YES,OUTPUT=(*.O1)