Output phase

The following describes the Output Phase processing.

Table 1. Output Phase Processing
Step	Processing	Exit Used
1	The $QGET service searches the job queue to find a candidate for output processing. Exit 14 ($QGET) is taken before a job is selected so this is not a job-related exit.	14
2	Because there can be multiple output processors, the job lock ($GETLOCK) provides serialization on a job basis. When the lock is obtained, the $JQE is checkpointed using the $CKPT macro.	$CKPT macro
3	After the job is selected and the job lock obtained, the job's $JCT is read from spool and Exit 7 is called.	7
4	If NOTIFY= was coded on the JOB JCL statement, NOTIFY processing calls Exit 16. This exit, is conditionally based on the job's JCL parameter.	16
5	After NOTIFY processing, the job's $IOTs are read from spool, $PDDBs are scanned, and the non-HELD $PDDBs are assigned to $JOEs. HELD $PDDBs are also assigned to $JOEs. $JOEs represent output groups, an output group can represent one or more spool data sets with like characteristics. Before each data set is grouped, Exit 40 is taken for each data set. Any changes made to the $PDDB will be used to determine data set grouping. Use Exit 40 to change SYSOUT characteristics. Exit 40 is taken before the data set has been gathered into an output group ($JOE). After all non-HELD PDDBs are processed, the $JCT is checkpointed. This is done to update the spool-resident $JCT with alterations made during output processing.	40
6	After the $JCT is checkpointed, the job's $JQE is moved to the hardcopy queue to await printing or other processing of job output. The $JQE is checkpointed after being moved to the hardcopy queue. Exit 51 is invoked when the job moves to the hardcopy queue.	51