NetBatch Manual

Commands
NetBatch Manual—522460-004
6-170
STATUS JOB Command
READY The job is available for execution. The scheduler selects it when an
executor associated with the job’s class is available and no RUNNEXT or
RUNNOW jobs are waiting.
The job remains in the READY state if its class has the attribute
INITIATION OFF or if the job was submitted when the scheduler has its
attribute INITIATION OFF. This attribute prevents jobs belonging to the
class from running. To make the jobs available for execution, change the
value of the INITIATION attribute to ON by using the ALTER CLASS or
ALTER SCHEDULER command.
RUNNEXT The job runs as soon as an executor associated with its class is available.
The scheduler selects the job ahead of READY jobs but after RUNNOW
jobs.
The job remains in the RUNNEXT state when an executor is available if
either of these conditions exists:
•
The job has the TAPEDRIVES attribute and requires more drives than
are available. For more information about this attribute, see
TAPEDRIVES Job Attribute on page 7-109 and TAPEDRIVES
Scheduler Attribute on page 7-110.
•
The job’s class has the attribute INITIATION OFF. This attribute
prevents jobs belonging to the class from running. To make the jobs
available for execution, change the value of the INITIATION attribute to
ON by using the ALTER CLASS command.
RUNNOW The job was the subject of a RUNNOW JOB command or has the AT
attribute. It is in this state momentarily until execution begins.
The job remains in the RUNNOW state if its class or scheduler has the
attribute INITIATION OFF. This attribute prevents jobs belonging to the
class from running. To make the jobs available for execution, change the
value of the INITIATION attribute to ON by using the ALTER CLASS or
ALTER SCHEDULER command.
SPECIAL-
n The job is on hold for one of these reasons:
•
The SUBMIT JOB command that submitted the job to the scheduler
specified the HOLD ON attribute.
•
An ALTER JOB command altered the value of the job’s HOLD attribute
from OFF to ON before the job ran.
•
The scheduler put the job on hold after it ran and stopped because the
job had the attribute HOLDAFTER ON.
•
The scheduler put the job on hold during execution because of a
problem requiring user intervention.
n indicates the reason the job is on hold and has one of these values. To
make any SPECIAL-n job available for execution, set the value of its HOLD
attribute to OFF.
Table 6-8. Job States (page 2 of 4)
State Description