Cap Mgt - No Sel

The non-SLM-managed job cannot run because it is not allowed to be selected when the system is at the current Capacity Level.

DELAY-ARM Restart.

The job is held for ARM restart, waiting for the system to restart.

DELAY-Active Other.

The job cannot run on this system because it is running or analyzing on another system in the JESplex.

DELAY-Active Here.

The job was not selected because it is still active on this system, possibly analyzing.

DELAY-BERT Locked.

The job cannot run because the JES2 control block that describes the job (JQE) is locked.

DELAY-BERTs short.

This job is delayed due to a shortage of BERTs. Access the Emergency Subsystem to relieve the BERT shortage.

DELAY-Busy Device.

The job was not selected because it is still busy on a device on this system.

DELAY-CFM Inactive

JLS cannot process the job yet because the Control File Manager component of TM is not active.

DELAY-Class Affin.

The class has a QAFF that does not include this system.

DELAY-Class Held -

The job cannot run because its execution class is held with a

$TJOBCLASS(x),HOLD=YES command.

DELAY-Class Limit.

The job cannot run because the maximum number of jobs allowed to execute in its class has been reached.

DELAY-DBS Affinity

The job cannot run because DBS has restricted the affinity of this job so that it does not include this system.

DELAY-DBS Dev Pool

The job cannot run because DBS has closed the device pools that the job requires.

DELAY-DBS Inactive

The job cannot run because it needs DBS services but the DBS application is not active.

DELAY-DBS Pacing

The job has been temporarily delayed by DBS to allow timely processing of device pools.

DELAY-DBS Workgrp

The job cannot run because DBS has closed the workgroup pools that the job requires.

DELAY-DJC Held CBM

The job is held by DJC from Cybermation.

DELAY-HELD Duplic.

The job is held by JES2 because its name duplicates that of a running job.

DELAY-HELD Operatr

The job was submitted with TYPRUN=HOLD or has been held by the operator.

DELAY-HELD Resourc

DELAY-HELD ThruPut

DELAY-Independent.

The job cannot run because it requested independent mode and this system is not in that mode, or it did not request independent mode and this system is in that mode.

DELAY-JCS AFTER --

The job cannot run because the job it must run AFTER has not completed.

DELAY-JCS BEFORE -

The job cannot run because the job that must run BEFORE it has not completed.

DELAY-JCS Sequence

This job cannot run because other jobs in the same batch have not completed yet or have not analyzed yet.

DELAY-JES2 Drained

The job cannot run because JES2 on this system is draining as a result of a $PJES2.

DELAY-JLS Agnt Err

Error accessing JLS Agent data.

DELAY-JLS Draining

The job cannot run because it is enqueued by JLS and the Agent is draining to allow a job with a weight of more than 1 to run.

DELAY-JLS Gbl.Lim.

The job cannot run because it is limited by JLS at the JESplex level.

DELAY-Inst. Veto

Installation Exit49 bypassed the job.

DELAY-JLS Sys.Lim.

The job cannot run because it is limited by JLS at the SYSTEM level.

DELAY-MHS Affinity

The MHS affinity does not include this system.

DELAY-No Initiator

The job cannot run because there is no available initiator with its class on this system.

DELAY-No sys (IND)

No active system in IND mode match this job’s affinity.

DELAY-No sys (AFF)

No active systems match this job’s affinity.

DELAY-No sys (MLS)

No active systems match this job’s SECLABEL affinity.

DELAY-SCHENV Affin

The job cannot run because the Scheduling Environment does not include this system.

DELAY-SECLABEL Aff

The job cannot run because the Multi-Level Security affinity (SECLABEL) does not include this system.

DELAY-Spin I/O ---

The job cannot run because some spun output is being processed. This can only occur if the job has been restarted.

DELAY-Spool Offln.

The job cannot run because some of its data or control blocks are on an offline SPOOL volume.

DELAY-TMSS Inactve

The job cannot be analyzed or run because TMSS is not active.

DELAY-WITH Job MAS

The job cannot run because the job it needs to run WITH is not active in the JESplex.

DELAY-WITH Job SYS

The job cannot run because the job it needs to run WITH is not active on this system.

DELAY-Wrong Affin.

The job cannot run because this system is not in the list of systems that it can run on.

DELAY-XEQ Stopped.

The job cannot run because execution on this system has been stopped with a $PXEQ command.

-SLM- <Sel Pt/Load

The job cannot run because its SLM selection priority is too low for selection due to the current load in the JESplex.

-SLM- <Sel Pt/Ovrd

The job cannot run because its SLM selection priority is below an overriden SLM selection point.

-SLM- <Sel Pt/SvGp

The job cannot run because its SLM selection priority is below its minimum value for selection.

-SLM- ACM SCl Perf

Job cannot be selected on this system due to the performance of the ACM Service Class.

-SLM- Aff Res Load

The job cannot run on this system due to the current load in the JESplex.

-SLM- Bad Svc. Grp

The job cannot run because it has a Service Group name that is no longer known to SLM.

-SLM- Cap - Max CC

The job cannot run because the Control Center assigned to this job is already running the maximum number of jobs specified for the current Capacity Level.

-SLM- Cap - Max Job

The job cannot run because the Service Group assigned to this job is already running the maximum number of jobs specified for the current Capacity Level.

-SLM- Cap - No Sel

The job cannot run because it is currently not allowed to be selected when the system is at the current Capacity Level.

-SLM- Cap - Sel Pt

The job cannot run because it is currently below the selection point required to be selected when the system is at the current Capacity Level.

-SLM- IPL boost

Job selection was last attempted during IPL Boost and did not meet criteria set in the SLM Policy for selection.

-SLM-Init Lmt SLM

The number of executing jobs for the job class, including SLM jobs that originally ran in that class has reached the count of JES2 initiators set to this class.  This rejection reason applies only to non-SLM managed jobs.

-SLM- Maximum Jobs

The job cannot run because the maximum number of Service Level Managed jobs has been reached.

-SLM-JPX Cls Lmt

The count of executing jobs for this job class, including SLM jobs that originally ran in that class, has reached the JESplex maximum set in JES2 for the class.  This rejection reason applies only to non-SLM managed jobs.

-SLM- Not Proc yet

The job is a Service Level Managed job that has not been processed by SLM yet but an attempt was made to select it.

-SLM- Not SLM Job

The job is in a Service Level Manager class but is not an SLM job. It cannot run unless the class is added to a non-SLM initiator.

-SLM- Not SLM clas

The job is a Service Level Managed job but was seen by a non-SLM initiator. The SLM class should be removed from all non-SLM initiators once all non-SLM jobs in those classes have been processed.

-SLM- OPP - Max CC

The job cannot run because the Control Center assigned to this job is already running the maximum number of jobs specified for Online Performance Protection.

-SLM- OPP - Max Jb

This job cannot run because the Service Group or Production Service Group assigned to this job is already running the maximum number specified for Online Performance Protection.

-SLM- OPP SCl Perf

This job cannot be selected on this system. The OPP Service Class assigned to this job is not performing well.

-SLM-Orig cls aff

Affinity for the original, non-SLM job class for the job does not include the local system.

-SLM-Orig cls hld

The original, non-SLM job class for the job is set as held in JES2. 

-SLM-Orig cls lmt

The original, non-SLM job class for this job has reached the maximum executing jobs allowed for either the JESplex or the local system.

-SLM- RP Boost

Job selection was last attempted during a Recovery Process Boost and did not meet criteria set in the SLM Policy for selection.

-SLM- RP Boost ACM

Job selection was last attempted during a Recovery Process Boost and was not allowed as the job was assigned to an ACM service class.

-SLM- SD Boost

Job selection was last attempted during Shutdown Boost and did not meet criteria set in the SLM Policy for selection.

-SLM- Sel. halted

The job cannot run because it is Service Level Managed and SLM job selection has been halted.

-SLM- SLM CPU max

The job cannot run as the CPU maximum set in the SLM policy for General Services or for specific Service Group has been reached.

-SLM- SLM disabled

The job cannot run because it is Service Level Managed and SLM has been disabled.

-SLM- SLM Sys Load

The job cannot run due to heavy load in this system.

-SLM- Srv Cls Perf

Job cannot be selected on this system due to the performance of the Service Class.

-SLM-Srv cls QAFF

Affinity for the original, non-SLM service class for the job does not include the local system.

-SLM-Sys Cls Lmt

The count of executing jobs for this job class, including SLM jobs that originally ran in that class, has reached the local system maximum set in JES2 for the class.  This rejection reason applies only to non-SLM managed jobs.

-SLM-Sys Storage

Job was not selected due to a shortage of either Auxiliary or Pageable Storage.