Because TSO/E jobs are submitted randomly, and may cause poorer turnaround for other batch jobs, you might want to use a separate job class for TSO/E jobs. If you are using JES2, use the INTRDR initialization statement to specify a job class to be used for all TSO/E jobs. For JES3, you can use the IATUX28 exit to override the class users specify in their JCL and direct TSO/E jobs to a separate class.

To specify a job class to be used for jobs submitted by individual users, use either the ACCOUNT command or the RACF® ADDUSER or ALTUSER command depending on whether the user information is defined in the UADS or RACF data base. The job class you specify using these commands overrides the class specified on the JES initialization statement.

For more information about these initialization statements and commands, see the following books:

• For the JES2 initialization statement, see .
• For the JES3 exit, see .
• For the ACCOUNT command, see .
• For the RACF ADDUSER and ALTUSER commands, see .