NJE hardcopy phase exits

The following describes the NJE Hardcopy Phase processing:

Table 1. NJE Hardcopy Phase Processing
Step	Processing	Exit Used
1	The Network SYSOUT Transmitter initializes a SYSOUT Transmitter device ($DCT) and acquires resources (lines, buffers, and so on.) to prepare for SYSOUT transmissions. The $#GET service routine is used to search the Job Output Table ($JOT) to find an eligible $JOE on the network queue. When a candidate is found the $CBIO macro is used to read the $JCT, $IOTs and $SWBITs from spool. Exit 7 or 8 is taken for each control block read. If the network job header does not exist, the NJE SYSOUT transmitter builds it.	Exit 7 (JES2 main task), Exit 8 (TCP/IP NJE)
2	The $NHD (Network Job Header) is then read from spool. $NHD Validation Routine (NJEHDVAL) is called to validate the NJE header structure before transmission. After validation, Exit 46 or 56 is taken. This exit allows the viewing, removing, or alteration of sections in the Network Job Header.	Exit 46 (JES2 main task), Exit 56 (NJE/TCP)
3	A $SEAS (JES2 Security Authorization Service) authorization check is made for each data set to be transmitted. This call to the SAF typically passes, because of the writer check previously done during the execution phase. The reason that this call should not fail is that a SAF call was made to the WRITER class during SYSOUT allocation at job execution time. If the job owner does not have authority to create SYSOUT destined for a particular node the job will fail in execution. Another Exit 46 or 56 is taken for each data set header followed by the data itself.	Exit 46, or Exit 56
4	Exit 46 or 56 is taken again for the job trailer. If the NJE job trailer does not exist, the NJE SYSOUT transmitter builds it. In general, the $#REM macro is used to remove the $JOE from the $JOT output queue.	Exit 46, or Exit 56
5	The data set is purged ($#PURGE) and if the device is a Spool Offload SYSOUT Transmitter, an SMF24 record is created. When using SPOOL Offload, the $JOE could remain on the $JOT and the data set may not be purged if the installation specified an output disposition where the output would not be purged after processing.