Specifying whether jobs are delayed for processing

By default, jobs submitted by TSO/E users are not held for later processing by an operator. You may want to hold TSO/E jobs for the following reasons:

Usually there is a trade-off between the performance of batch and on-line processing, so you may want to perform your batch processing off-shift, when it does not degrade the performance of on-line users
Some jobs require tapes, so you may want to hold those jobs until the tapes are available and have been mounted. If you do not hold the jobs, they tie up resources until the tapes are available.

You can use JES2 or JES3 initialization statements to specify that only certain job classes are held. However, you can specify that all jobs submitted by TSO/E users are held by using the JES2 INTRDR initialization statement. To specify a held class used for jobs submitted by individual users if they omit the job class in their JCL, use either the ACCOUNT command or the RACF® ADDUSER or ALTUSER command depending on whether the user is defined in the UADS or RACF data base.