If a job generates a SYSOUT data set and specifies “HOLD=YES” on the DD statement for the data set, the “hold” takes effect on the system which receives the data set. If the job's execution node and the data set's destination node are the same, JES2 performs the hold as soon as the job deallocates the data set. If the job's execution node differs from the job's destination node, JES2 removes the local hold on the data set. This permits JES2 to group the data set into an output group; JES2 then places the output group on the network queue for output groups. The SYSOUT transmitter then selects the data set for transmission.

When JES2 transmits a held data set (possibly at the same time it transmits the job's other data sets), the data set header will reflect the hold status of the data set. When a node receives a SYSOUT data set marked as held, the SYSOUT receiver checks the data set's destination against its own node name. If the data set destination is the receiver's node, the receiver performs normal held data set processing. A TSO/E user can then inspect the data set. When an operator or TSO/E user releases the held data set, the system no longer holds the data set even though the operator or TSO/E user changed its destination before printing the data set. At each point along the way, you can use the JES2 $R command to change the data set's destination.