NetBatch Manual

Attributes
NetBatch Manual—522460-004
7-105
STOP-ON-ABEND Job Attribute
jobnumber: 501
startup: LABEL XYZ, PURGE, LIMIT 3:00
STOP-ON-ABEND Job Attribute
The STOP-ON-ABEND job attribute determines whether the scheduler stops a job and
all its processes if any process of the job terminates because of CPU failure; abends
with any completion code; or stops with completion code -3, -2, -1, 2, 3, 4, 5, or 6. The
attribute works in combination with the job’s IFFAILS, RESTART, and STALL attributes.
OFF
causes the scheduler to treat the job according to:
•
The job’s IFFAILS, RESTART, and STALL attributes
•
Whether the job is recurrent or nonrecurrent (a recurrent job has the
CALENDAR or EVERY attribute)
•
The cause of the failure (for example, the executor-program process
abends)
For more information, see Table 4-5 on page 4-28, IFFAILS Job
Attribute on page 7-64, RESTART Job Attribute on page 7-95, and STALL Job
Attribute on page 7-102.
ON
causes the scheduler to stop the job when any process of the job terminates,
abends, or stops. The stopped job’s state depends on the values of the job’s
IFFAILS, RESTART, and STALL attributes. For more information, see Figure 4-9 on
page 4-29.
Considerations
•
A job submitted without the STOP-ON-ABEND attribute adopts the DEFAULT-
STOP-ON-ABEND scheduler attribute. To display the value of this attribute, use
the INFO SCHEDULER command.
•
A failed process of a job with the STOP-ON-ABEND ON attribute does not stop the
job if dissociated from it by the TACL RUN command option JOBID or by the
JOBID-ZERO job attribute.
•
Both processes of a process pair must cease to exist before the STOP-ON-ABEND
ON attribute takes effect.
S[TOP]-[ON]-[ABEND] { OF[F] | ON }
Note. An executor-program process that is not a TACL process might start new processes
before the scheduler receives the terminate, abend, or stop message. To prevent these
new processes from starting, make the executor program test the completion code of each
process before starting the next process.