Unicenter CA-Scheduler Job Management for VSE User Guide
Unicenter CA-Scheduler Job Management for VSE User Guide
Unicenter CA-Scheduler Job Management for VSE User Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
4.2 Displaying Status<br />
Code Reason For Error<br />
88 Of a CMS service machine access error<br />
8C<br />
Of a CMS service machine punch error<br />
90 The CLOSE failed<br />
94 PFIX failed<br />
98 SCHEDULER/DRIVER variable resolution error<br />
9C<br />
Of a CMS service machine invalid record length<br />
A0<br />
Of a CMS service machine error unpacking file<br />
A4<br />
JCLMAN member not found or syntax error<br />
A8<br />
<strong>User</strong>id not defined to <strong>CA</strong>-TOP SECRET<br />
SUBMITD<br />
UNKNOWN<br />
The JCL <strong>for</strong> CPU jobs has been submitted to the operating<br />
system <strong>for</strong> execution and has not started. The POWER job<br />
number also displays with this status.<br />
This job was either STARTED or SUBMITD when the system<br />
failed. It was not in a power reader queue when <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> started up again; there<strong>for</strong>e it was assigned this<br />
status. It can be resubmitted by issuing a SUBMIT, RERUN, or<br />
FORCE command. It can also be canceled or posted as<br />
complete.<br />
WAITING FOR CPU JOB<br />
This job will not start at a post-CPU station until it has ended<br />
at the CPU station.<br />
WAITING FOR PRED<br />
The job or schedule has reached its early start time and is<br />
waiting <strong>for</strong> one or more of its predecessor conditions to be<br />
satisfied. These predecessor conditions include the start or end<br />
of another job or schedule, the close of an output data set or<br />
the satisfaction of a global variable. (You can use WAIT,<br />
AND REASON on the Online Status panel to find out what<br />
this job or schedule is waiting <strong>for</strong>.) This job or schedule will<br />
not run until all of its predecessor conditions are satisfied<br />
unless it is <strong>for</strong>ced using the FORCE command.<br />
WAITING FOR RESOURCES<br />
The job has reached its early start time and all of its<br />
predecessor conditions have been satisfied. Now it is waiting<br />
<strong>for</strong> a DASD volume to be mounted, <strong>for</strong> a data set (SEPARATE<br />
DSNAME), or <strong>for</strong> jobs from which it is separated to complete<br />
(SEPARATE JOBS). (You can use WAIT, AND REASON on<br />
the Online Status panel to find out what this job is waiting<br />
<strong>for</strong>.) It will not run until these resources are available unless it<br />
is <strong>for</strong>ced using the FORCE command.<br />
Chapter 4. Online Monitoring 4-21
Change language