DO SYSOUT Handling Operations

The SYSOUTs that are affected by SYSOUT handling operations are determined by whether the SYSOUTs are under JES2 or JES3, as described in the following table.

Table 188 Varying Effect of SYSOUT Handling Operations

Operation	Effect
Under JES2:	Operations are performed on all of the held SYSOUTs, or held portions of SYSOUTs, of the job, unless otherwise restricted to a specific FROM class by the FRM subparameter.
Under JES3:	Operations are performed only on the SYSOUTs of the job in the Control-M held class, as specified in the Control-M installation HLDCLAS parameter.

Operation

Effect

Under JES2:

Operations are performed on all of the held SYSOUTs, or held

portions of SYSOUTs, of the job, unless otherwise restricted to a

specific FROM class by the FRM subparameter.

Under JES3:

Operations are performed only on the SYSOUTs of the job in the

Control-M held class, as specified in the Control-M installation

HLDCLAS parameter.

SYSOUT handling operations are listed below:

Copying SYSOUTs to a file (OPT=F)
The SYSOUTs of the job are copied (not moved) to the file specified in the data subparameter.

The file name specified in the data subparameter can contain AutoEdit System variables, and user-defined AutoEdit variables that are defined in the job scheduling definition or the IOA Global Variable database, or are loaded into AutoEdit cache. If the AutoEdit variables cannot be resolved, the sysout is not copied.

Control-M allocates the file with DISP=(NEW,CATLG,DELETE) using the unit and space attributes specified in the Control-M installation parameters. While the block size (BLKSIZE) is automatically calculated by Control-M, the logical record length (LRECL) is copied from the input SYSOUT file. The maximum LRECL allowed is 256 characters.

SYSOUTs can be archived by copying them. However, to reduce overhead, this method is recommended only for small sysouts.
Deleting SYSOUTs (OPT=D)
The SYSOUTs of the job are deleted (purged) from the output queue.

Note: This operation works on all SYSOUTs under JES2 or JES3 (regardless of held status or class) unless otherwise restricted by the FRM subparameter.
Releasing SYSOUTs (OPT=R)
The SYSOUTs of the job are released for printing.
Changing the class of SYSOUTs (OPT=C)
The SYSOUTs of the job are changed to the output class specified in the data subparameter. Ensure that you specify a meaningful target output class.

Note the following points:
- Changing a SYSOUT class to a non-held class does not release the SYSOUT because the SYSOUT attributes do not change (due to JES logic).
  To ensure that the SYSOUT is released, use DO SYSOUT statements to release the SYSOUT after changing its class. For example:
  
  DO SYSOUT OPT C PRM R FRM A
  
  DO SYSOUT OPT R PRM FRM A
- Changing a SYSOUT class to a dummy class does not purge the SYSOUT because the SYSOUT attributes do not change (due to JES logic).
- To save the original MSGCLASS of a job and to restore it at output processing time, specify a data value of *. The SYSOUTs are changed to the original class of the job.
Moving SYSOUTs to a new destination (OPT=N)
The SYSOUTs of the job are moved to the output destination specified in the data subparameter. Ensure that you specify a meaningful target output destination.

Parent Topic

DO SYSOUT: Post-Processing Parameter