Unicenter CA-Scheduler Job Management for VSE User Guide

3.9 Defining Jobs
3.9.3.7 Once a Job Starts, How Can You Intervene?
Unicenter CA-Scheduler offers several commands that allow users to control a
job, but a job's definition also allows you to define control points during a job's
processing. Ordinarily, you do not want to intervene in job processing.
However, Unicenter CA-Scheduler gives you that ability should you need it.
MEMO defines text to display at the system console when this job starts at the
CPU. This happens every time that job runs. A MEMO of up to 60 characters
forces the operator to reply OK or TERM. If the reply is OK, the job runs, but
a reply of TERM causes Unicenter CA-Scheduler to cancel the job.
Although manual intervention is what Unicenter CA-Scheduler tries to
eliminate, there may be times when you need it. For example, Unicenter
CA-Scheduler may control a job that needs to have an online database closed
to users before it starts. Or another job may need onsite approval before it
starts. These instances show how the MEMO option can be used.
MEMO allows you to control a job when it starts, and INTERRUPT gives you
control when a job ends. INTERRUPT = YES prevents a job from automatically
being posted COMPLETED even though it ended successfully. Instead, it's
given a status of INTRPTD which prevents the job's successors from being
posted as satisfied. That gives you the chance to review the job's output. For
example, you can check a trial balance to see if it is correct. If so, you can
change the job's status to ENDED so its successors can be reevaluated to see if
they can run, but if you are not satisfied with the output, you can rerun an
interrupted job using the RERUN or SUBMIT command.
3.9.3.8 What Happens When Jobs Don't End Successfully?
Several fields on the job base record determine what happens when something
goes wrong or when unusual circumstances occur:
■
■
■
■
ABEND
BACKLOG
FAIL CODE
RECOVERABLE
What if the system crashes while a job is running? Will Unicenter
CA-Scheduler automatically restart the job? RECOVERABLE on the job record
tells Unicenter CA-Scheduler if a job can be restarted after the system is
re-IPLed. RECOVERABLE defaults to NO, which causes Unicenter
CA-Scheduler to put the job on hold. The job waits to be canceled or released,
but if RECOVERABLE = YES, Unicenter CA-Scheduler automatically releases
the job after you restart the system.
What if a job abends (cancels without going to normal completion)? A job's
ABEND field allows a variety of things to happen:
3-68 Unicenter CA-Scheduler User Guide