|
|
|
|
|
When the DO SYSOUT statement is specified, Control-M/Analyzer tries to execute the DO SYSOUT instruction.
The DO SYSOUT statement can be invoked from an EXECUTE block containing any type of ON statement (ON CLASS, ON DATA, and so on).
DO SYSOUT processing is performed only on closed sysout files that are in HELD state after being created by previous steps of the job (for example, FREE=CLOSE was specified in the DD statement that created the sysout files).
If the FRM (from class) parameter is blank, all of the held output of the job is processed. When the FRM parameter is specified, only held sysouts that belong to the selected class are processed.
Table 247 Examples of Processing Job Sysout Field Settings
Value |
Description |
|---|---|
OPT=D |
Delete. The held sysouts of the job are deleted (purged) from the output queue. |
OPT=R |
Release. The held sysouts of the job are released for printing. |
OPT=C PRM=class |
The held sysouts of the job are moved to the specified output class. The user must specify an existing, meaningful output class. |
OPT=N PRM=newdest |
The held sysouts of the job are changed to a different output destination. The user must specify an existing, meaningful output destination. |
Note: At JES3 sites, BMC recommends that the FRM parameter be specified (for example, FRM should not be blank) because operations on all of the held output of the jobs cannot be performed in one DO SYSOUT operation. To process the held sysouts of all jobs, specify separate DO SYSOUT statements for each output class.
Parent Topic |