This appendix identifies the JES2 job-related exits. It also describes the relationship between the JES2 $JCT and MVS/SP JMR blocks and provides an overview of the security access service.

Examples of exits that are not job-related are exits such as those taken during JES2 initialization, JES2 termination, RJE signon, JES2 command processing, and other functions not necessarily related to individual jobs ¹.

Job-related exits fall into two categories: specific purpose and general purpose. A specific purpose job-related exit is one that provides a specific function. Although, it may be used for other purposes such as a compromise to avoid in-line modifications.

Examples of specific-purpose job-related exits are job output overflow (Exit 9) and spool partitioning exits (Exits 11 and 12). These exits are used in controlling output limits and spool allocation (fencing) for a particular job. Because these exits do not occur at predictable intervals during the life of a job, using them for a general purpose is not appropriate.

General-purpose job-related exits are exits such as the job statement scan exit (Exit 2), converter internal text scan exit (Exit 6), and the control block read/write exits (Exits 7 and 8). These exits are typically considered when there is a user requirement to control installation standards, job resources, security, output processing, and other job-related functions.

Often the use of more than one exit is required and sometimes combinations of JES2 and other exits such as Systems Management Facilities (SMF) exits must be used. Table 1 lists the exits that are discussed. They are not all of the job-related exits but possibly enough to make a decision as to which exits to choose to control certain processes or functions during the life of a job.