NetBatch Manual

Attributes
NetBatch Manual—522460-004
7-121
WAITON Job Attribute
°
Execute an explicit or implicit $RELEASE commandif the master job’s
executor program is an NBEXEC process. NBEXEC automatically executes an
implicit $RELEASE * command if the job runs without errors.
°
Execute the NetBatch programmatic command RELEASE JOB.
°
Terminate normally (if the dependent has the attribute WAITON master-job
STOP or WAITON master-job STOP-ABEND) or abnormally (WAITON
master-job STOP-ABEND).
For information about the ZBAT:RELEASE macro and $RELEASE command, see
Section 4, Job Planning, Submission, and Management. For information about the
RELEASE JOB command, see the NetBatch Management Programming Manual.
•
Use the RELEASE-WAITON command to release dependent jobs from their
masters without running the masters. For more information, see RELEASE-
WAITON Command on page 6-115.
•
A dependent job can depend on masters from its own scheduler and from other
local and remote schedulers. (However, the dependent job must be in the same
scheduler as the master job when case specifies STOP or STOP-ABEND.) To set
up a dependency between a dependent job on one scheduler and a master job on
another:
1. Assign the WAITON attribute to the dependent job, specifying for job-name
the name of the master job. (job-name cannot specify the master job’s
scheduler. Use the ZBAT:RELEASE macro or $RELEASE command for this.)
2. Add the ZBAT:RELEASE or $RELEASE job-release command to the master
job’s input file, specifying the dependent job’s scheduler and name. When the
master job runs, it releases the specified dependent job.
•
A dependent job cannot determine the schedulers of its masters because its
WAITON attribute specifies master job names only. As a result, the dependent job
can receive its release from any master running in any scheduler. For this reason,
use unique names for all master and dependent jobs, regardless of the nodes on
which they run.
•
For an effective dependency to exist between two recurrent jobs, the dependent
job should have the same execution interval as its master. (A recurrent job has the
CALENDAR or EVERY attribute.) For example, a dependent job whose master has
the attribute EVERY 21 DAYS should also have the attribute EVERY 21 DAYS.
What happens when the execution interval differs depends on whether the master
runs more or less frequently than the dependent:
°
If the master runs more frequently than the dependent, it releases the
dependent each time it runs. As a result, the dependent runs only at its
specified execution interval despite having received perhaps many releases
from the master.