In a network, you can route sysout data sets from any node or work
station to any node or work station.
A sysout data set is printed or punched at the submitting location
unless:
- The job was submitted from TSO and routed to the NJE network for
execution. Unless overridden by the //*MAIN ORG parameter or directed
by a destination parameter, the sysout data set will be routed to
the node from which the job was submitted and the destination ANYLOCAL.
- The sysout data set destination was changed by the ORG parameter
on the MAIN statement, or by a destination parameter.
To route a sysout data set to another location, use the following:
- DEST parameter on DD SYSOUT statement
- Specifies the destination for the sysout data set being defined.
- DEST parameter on OUTPUT JCL statement
- Specifies the destination for all referencing sysout data sets.
- ORG parameter on //*MAIN statement
- Specifies an origin group, network node, or remote work station
for the job's sysout data sets.
Output destination when remote job processing
in JES3
For jobs from remote work stations submitted through remote job
processing (RJP), the sysout data sets are returned to the originating
work station unless another destination is requested in a //*MAIN
statement with an ORG parameter, OUTPUT JCL statement, or DD statement.
Examples
//DDFAR DD SYSOUT=E,DEST=NYC
//OTFAR OUTPUT DEST=NYC,COMPACT=TABCM
//DD1 DD SYSOUT=E,OUTPUT=*.OTFAR
//JEX3 JOB ,'MAIL A60'
//*MAIN ORG=NYC
//S3 EXEC PGM=GHI
//DD4 DD SYSOUT=E