When jobs end at the same time

Sometimes, jobs end at the same time. For example, a network error occurs and the job attributes are set to *ENDJOB or *ENDJOBNOLIST. In addition to the job ending, the following device recovery actions occur.

• The job's priority is lowered. This occurs so the job is no longer at the same priority as the other active interactive jobs.
• The job's time slice is set to 100 milliseconds. This occurs to give higher priority jobs a better chance of getting processing resources.

Job logs for jobs with job attributes set to *ENDJOB or *ENDJOBNOLIST are in job log pending. To produce printer output from a job log that is in job log pending, use the Display Job Log (DSPJOBLOG) command.

When a job ends you can control how the job log is written to a spooled file. This can be done by the job itself while it is ending, by a background server job, or not at all. The value that you specify can have a significant impact on overall recovery time when many jobs end at the same time. For more information, see the related concept Job log pending.