NetBatch Manual

Commands
NetBatch Manual—522460-004
6-129
RUNNOW JOB Command
•
The scheduler creates temporary executors for all jobs with the AT attribute and for
all jobs that are operated on by the RUNNOW JOB command. The scheduler
deletes the executors when the jobs finish.
•
A temporary executor has a scheduler-assigned name of the form
__TEMP_EXEC_ job-number, where job-number is the number of the job
using the executor; for example, __TEMP_EXEC_496.
•
The scheduler selects the CPU of a temporary executor from available CPUs on
the scheduler’s node.
•
A job that is subject to a RUNNOW JOB command does not run if any 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.
°
The scheduler would exceed its temporary-executors limit by running the job.
In this case, the job runs when the scheduler can create a temporary executor
without exceeding the limit. For more information, see MAX-CONCURRENT-
JOBS Scheduler Attribute on page 7-79.
•
You can omit the object keyword JOB from the RUNNOW JOB command only
when JOB is the current assumed object. For more information, see ASSUME JOB
Command on page 6-72.
•
If the scheduler’s INITIATION attribute is OFF, the RUNNOW command does not
run the jobs submitted to the scheduler. After RUNNOW is issued, the jobs are in
the RUNNOW state until the scheduler INITIATION attribute is set to ON using the
ALTER SCHEDULER command.
Example
This example shows the submission of a job to a scheduler that has no executors. The
RUNNOW JOB command makes the scheduler run the job in a temporary executor,
which the scheduler deletes when the job finishes. The example lists the scheduler log-
file events that record job submission, temporary-executor creation, job execution, and
so on.
53> BATCHCOM $ZBAT; STATUS EXECUTOR *
2117-I No EXECUTOR selected
54> BATCHCOM $ZBAT; SUBMIT JOB, EXECUTOR-PROGRAM DELAY,
STARTUP
"1 MINS"
Job ZBAT-0082 Jobnumber 82 submitted
55> BATCHCOM $ZBAT; STATUS JOB *