Exceptional jobs

A job is deemed exceptional when the statistics for that job are unreliable or unrepresentative of the service the workload as a whole is experiencing; they are removed from the aggregate calculations for the workload. The Service Delivered field has a value Indeterminate, with more information at the bottom of the Job Summary Report. The reasons for any delays are still included in the Job Summary Report as well as the EQT and AQT for that job.

A job is flagged as exceptional when one or more of the following conditions are encountered:

• A job with the same name is already queued for execution, and the installation has chosen to delay duplicate jobs. It does not matter if the duplicate job name results in an actual delay. Since SLM cannot predict the eventual effect, the job is treated as exceptional.
• The job was started with the /SLM START operator command.
• The job was requeued for execution with the $EJ JES2 command.
• An IPL has caused the job to be requeued for execution.
• A new SLM Policy was activated, resulting in a change to the Service Group definition for the job that affects one or more of aging limits, aging rates, job limits, or CPU constraints.
• Operator resets the Service Class for the job.

A job can be exceptional for more than one of these reasons. SLM tracks all of them, but only the first reason encountered is reported in the Job Summary Report.