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
4.2 Displaying Status The last two characters tell you why the submission failed: Code Reason For Error 04 The member could not be found 10 A file opening failed 18 Support was not generated for this library 1C A READ failed 20 Of an internal CATMAN I/O error 24 Internal to Unicenter CA-Scheduler 28 Job name is invalid 2C Internal to Unicenter CA-Scheduler 30 Internal to Unicenter CA-Scheduler 34 Class is invalid 38 Internal to Unicenter CA-Scheduler 3C PRI is invalid 40 SYSID is invalid 44 Unicenter CA-Scheduler ran out of storage 48 POWER communication error - IDENT 4C POWER communication error - CONNECT 50 POWER communication error - SENDR 54 POWER communication error - REQUEST 58 A logic error has occurred 5C Appendage error/CTLSPOOL error 60 An error from the CMS SUBMIT 64 The member is empty (no records) 68 Allfusion CA-Vollie SUBMIT no librarian support 6C Allfusion CA-Vollie INCLUDE not found 70 AllFusion CA-Librarian/CA-Panvalet INCLUDE not found 74 Too many nested INCLUDEs 78 Error on INCLUDE statement 7C LIB link error (bad VCON) 80 The CMS service machine is not logged on 84 The CMS service machine is not receiving 4-20 Unicenter CA-Scheduler User Guide
4.2 Displaying Status Code Reason For Error 88 Of a CMS service machine access error 8C Of a CMS service machine punch error 90 The CLOSE failed 94 PFIX failed 98 SCHEDULER/DRIVER variable resolution error 9C Of a CMS service machine invalid record length A0 Of a CMS service machine error unpacking file A4 JCLMAN member not found or syntax error A8 Userid not defined to CA-TOP SECRET SUBMITD UNKNOWN The JCL for CPU jobs has been submitted to the operating system for execution and has not started. The POWER job number also displays with this status. This job was either STARTED or SUBMITD when the system failed. It was not in a power reader queue when Unicenter CA-Scheduler started up again; therefore it was assigned this status. It can be resubmitted by issuing a SUBMIT, RERUN, or FORCE command. It can also be canceled or posted as complete. WAITING FOR CPU JOB This job will not start at a post-CPU station until it has ended at the CPU station. WAITING FOR PRED The job or schedule has reached its early start time and is waiting for one or more of its predecessor conditions to be satisfied. These predecessor conditions include the start or end of another job or schedule, the close of an output data set or the satisfaction of a global variable. (You can use WAIT, AND REASON on the Online Status panel to find out what this job or schedule is waiting for.) This job or schedule will not run until all of its predecessor conditions are satisfied unless it is forced using the FORCE command. WAITING FOR RESOURCES The job has reached its early start time and all of its predecessor conditions have been satisfied. Now it is waiting for a DASD volume to be mounted, for a data set (SEPARATE DSNAME), or for jobs from which it is separated to complete (SEPARATE JOBS). (You can use WAIT, AND REASON on the Online Status panel to find out what this job is waiting for.) It will not run until these resources are available unless it is forced using the FORCE command. Chapter 4. Online Monitoring 4-21
- Page 141 and 142: 3.9 Defining Jobs DESTINATIONS and
- Page 143 and 144: 3.9 Defining Jobs For These Message
- Page 145 and 146: 3.9 Defining Jobs To Separate All J
- Page 147 and 148: 3.9 Defining Jobs 3.9.4.6 Defining
- Page 149 and 150: 3.10 Displaying and Updating a Job
- Page 151 and 152: 3.10 Displaying and Updating a Job
- Page 153 and 154: 3.10 Displaying and Updating a Job
- Page 155 and 156: 3.11 Deleting Job Records 3.11 Dele
- Page 157 and 158: 3.11 Deleting Job Records SCHD-JM
- Page 159 and 160: 3.12 Analyzing Jobs 3.12 Analyzing
- Page 161 and 162: 3.12 Analyzing Jobs To display a fu
- Page 163 and 164: 3.13 Automatic Console Replies for
- Page 165 and 166: 3.13 Automatic Console Replies for
- Page 167 and 168: 3.13 Automatic Console Replies for
- Page 169 and 170: 3.14 Summary of Job Maintenance 3.1
- Page 171: 3.14 Summary of Job Maintenance To
- Page 174 and 175: 4.1 Online Monitoring Panel 4.1 Onl
- Page 176 and 177: 4.1 Online Monitoring Panel This ch
- Page 178 and 179: 4.2 Displaying Status Schedules and
- Page 180 and 181: 4.2 Displaying Status The table fol
- Page 182 and 183: 4.2 Displaying Status To Restrict T
- Page 184 and 185: 4.2 Displaying Status 4.2.4.1 Defau
- Page 186 and 187: 4.2 Displaying Status SCHD-CP SCHE
- Page 188 and 189: 4.2 Displaying Status If the schedu
- Page 190 and 191: 4.2 Displaying Status or backlogged
- Page 194 and 195: 4.2 Displaying Status WAITING FOR S
- Page 196 and 197: 4.3 Handling Messages If your messa
- Page 198 and 199: 4.4 Handling Predecessor Conditions
- Page 200 and 201: 4.5 Handling Global Parameters 4.5.
- Page 202 and 203: 4.7 Displaying Data Set Mask Names
- Page 204 and 205: 4.9 Controlling Schedules 4.9 Contr
- Page 206 and 207: 4.10 Controlling Jobs 4.10 Controll
- Page 208 and 209: 4.10 Controlling Jobs Enter RELE CA
- Page 210 and 211: 4.10 Controlling Jobs SCHD-DADP D
- Page 212 and 213: 4.11 Summing Up To Specify Abbrevia
- Page 214 and 215: 4.11 Summing Up This Command Affect
- Page 216 and 217: The criteria language uses three ty
- Page 218 and 219: 5.1 Criteria Vocabulary job. Normal
- Page 220 and 221: 5.1 Criteria Vocabulary Example SCD
- Page 222 and 223: 5.1 Criteria Vocabulary Given the e
- Page 224 and 225: 5.2 Calendar Mechanisms 5.2 Calenda
- Page 226 and 227: 5.2 Calendar Mechanisms 5.2.2.1 Wor
- Page 228 and 229: 5.2 Calendar Mechanisms Suppose you
- Page 230 and 231: 5.2 Calendar Mechanisms datetable o
- Page 232 and 233: 5.2 Calendar Mechanisms The panel f
- Page 234 and 235: 5.3 Some Examples 5.3 Some Examples
- Page 236 and 237: 5.3 Some Examples Example 7 A payro
- Page 238 and 239: 5.3 Some Examples ■ ■ If the la
- Page 240 and 241: 5.4 What Is Wrong with These Exampl
4.2 Displaying Status<br />
The last two characters tell you why the submission failed:<br />
Code Reason For Error<br />
04 The member could not be found<br />
10 A file opening failed<br />
18 Support was not generated <strong>for</strong> this library<br />
1C<br />
A READ failed<br />
20 Of an internal <strong>CA</strong>TMAN I/O error<br />
24 Internal to <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />
28 <strong>Job</strong> name is invalid<br />
2C<br />
Internal to <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />
30 Internal to <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />
34 Class is invalid<br />
38 Internal to <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />
3C<br />
PRI is invalid<br />
40 SYSID is invalid<br />
44 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> ran out of storage<br />
48 POWER communication error - IDENT<br />
4C<br />
POWER communication error - CONNECT<br />
50 POWER communication error - SENDR<br />
54 POWER communication error - REQUEST<br />
58 A logic error has occurred<br />
5C<br />
Appendage error/CTLSPOOL error<br />
60 An error from the CMS SUBMIT<br />
64 The member is empty (no records)<br />
68 Allfusion <strong>CA</strong>-Vollie SUBMIT no librarian support<br />
6C<br />
Allfusion <strong>CA</strong>-Vollie INCLUDE not found<br />
70 AllFusion <strong>CA</strong>-Librarian/<strong>CA</strong>-Panvalet INCLUDE not found<br />
74 Too many nested INCLUDEs<br />
78 Error on INCLUDE statement<br />
7C<br />
LIB link error (bad VCON)<br />
80 The CMS service machine is not logged on<br />
84 The CMS service machine is not receiving<br />
4-20 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>
Change language