JES2 exits and initialization statements

Table 1 and Table 2 summarize some of the JES2 exits and initialization statements you can use to customize TSO/E jobs.

Table 1. JES2 exits
JES2 exit	Description	Reference
Exit 2 (Job statement scan)	Use to tailor JOB JCL statements, supply additional JOB statement parameters, and modify job-related control blocks.
Exit 3 (Job statement accounting field scan)	Use to tailor JOB JCL accounting information, supply additional accounting field information, and modify job-related control blocks. (Although you can use Exit 2 to tailor accounting information, you can more easily access the information from Exit 3.)
Exit 13 (IDTF screening and notification)	Use to screen incoming files as they arrive at the receiver's network node. The exit can delete the file, route it to another user, or allow it to be sent to the target addressee.
Exit 20 (End of job input)	Use to cancel a job before it starts processing.
Exit 22 (Cancel/Status)	Use to tailor the way the TSO/E STATUS and CANCEL commands work.
Exit 38 (TSO/E RECEIVE Authorization)	Use during data set selection to determine whether the user has authority to receive the data.

Table 2. JES2 initialization statements
JES2 initialization statement	Description	Reference
INTRDR	Use to specify the characteristics to be used for jobs submitted through JES2 internal readers. You can specify defaults for processing jobs submitted by TSO/E users.
OUTCLASS	Use to specify the default characteristics that are to be used for processing SYSOUT data sets. You can specify: Whether data sets are to be held for processing by the TSO/E OUTPUT command. That the output class is to be punched (a requirement when using the TSO/E TRANSMIT and RECEIVE commands).
STCCLASS	Use to specify the default characteristics to be associated with all started tasks. If your installation uses the TSO/E TRANSMIT and RECEIVE commands, you need to specify that SYSOUT data is to be written for jobs executed in time sharing classes.
TSUCLASS	Use to specify default job processing characteristics that will be used for a user's TSO/E session. You can: Specify the default message class that will be used for TSO/E session logs. Identify the library that contains TSO/E logon procedures. Specify that SYSOUT data is to be written for jobs executed in time sharing classes (a requirement when using the TSO/E TRANSMIT and RECEIVE commands).