Unicenter CA-Scheduler Job Management for VSE User Guide

6.1 Commonly Asked Questions
users in the SEND START MESSAGES TO list defined on the job's Message
Definition panel.
6.1.2.8 What Are My Options When a Job Abends?
6.1.3 Analyzing the Database
In the next chapter, the separate topic Restart/Recovery Of Scheduled Jobs is
devoted to this topic.
This topic presents several questions you may have regarding analyzing the
database and gives you difinitive answers.
6.1.3.1 How Can I Prevent Predecessor Loops?
Predecessor loops are also called predecessor deadlocks. A predecessor
deadlock exists when two jobs end up requiring that the other execute first.
For example:
JOBA requires JOBX to run first.
JOBB requires JOBA to run first.
JOBX requires JOBB to run first.
JOBX is a predecessor of JOBA, but cannot run until JOBB has ended. Since
JOBB will not run until after JOBA has ended, there is a deadlock.
Imagine how complicated this would be to resolve if there were a hundred
jobs, each with many predecessors. It is difficult to detect a deadlock unless
you use the Analyze Report.
To obtain the Analyze Report, run the Unicenter CA-Scheduler Utility program
(CAJUTIL0) with the batch command ANALYZE. You can check specific jobs
or schedules or you can give a range of jobs or schedules. For example, you
can analyze all schedules that begin with the first three characters PAY.
Anytime you make significant changes to jobs or schedules, run this report to
ensure that your changes have not introduced deadlocks. You should produce
it any time the criteria for a job or schedule is changed.
Instead of getting the comprehensive Analyze Report, you can use the
LIST=NO operand to request that just the errors be reported.
The ANALYZE command can also be issued online from any of these panels:
■
■
■
■
Job Maintenance (SCHD-JM)
Job Directory (SCHD-JD)
Schedule Maintenance (SCHD-SM)
Schedule Directory (SCHD-SD)
6-10 Unicenter CA-Scheduler User Guide