JES3 exits and initialization statements

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

Table 1. JES3 exits
JES3 exit	Description	Reference
IATUX28	Use to tailor JOB JCL statements, supply additional JOB statement parameters, and modify job-related control blocks.
IATUX30	Use to tailor the use of the TSO/E OUTPUT, STATUS, and CANCEL commands.
IATUX33	Use to tailor JCL EXEC statements, JCL comment statements, and JES3 control statements. You can supply additional statements, and modify related control blocks.
IATUX34	Use to tailor JCL DD statements, and JCL comment statements. You can supply additional statements, and modify related control blocks.
IATUX38	Use to change the SYSOUT class for local SYSOUT data sets.
IATUX42	Use to accept or reject data sent via the TSO/E TRANSMIT command.
IATUX44	Use to tailor JCL statements other than JOB, EXEC, or DD statements.
IATUX60	Use to determine whether a data set that was to be received by a TSO/E user should be deleted or kept, if the TSO/E user can never log on to TSO/E with the proper security label to ever receive the data set.

Table 2. JES3 initialization statements
JES3 initialization statement	Description	Reference
SYSOUT	Use to specify SYSOUT class characteristics. If using the TSO/E TRANSMIT and RECEIVE commands, the output class must be punched.
CIPARMS	Use to specify a converter/interpreter options list, which defines defaults for JCL keywords, such as whether users must specify a programmer name or account number in JOB statements.
STANDARDS	Use to associate job processing characteristics with users' TSO/E sessions, and jobs submitted by users. You can specify: A set of defaults (a converter/ interpreter options list) that will be used for users' TSO/E sessions, and for jobs submitted by TSO/E users. The library containing the TSO/E logon procedures.