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
7.3 Issuing Online Commands in Batch To have an appreciation for the flexibility of this capability, all of the different status codes are listed in the following tables. Major Minor Description ABENDED ACTIVE CANCEL CC=dd BACKLOG The job abended. The job abended with a completion code of X'dd' (for example, X'FF'). The schedule or job is active in the system. It is not necessarily running, but it is not on HOLD. The schedule or job was canceled: It carried over to the next production day as backlog COMPLETE OPER By an operator The schedule or job ran to completion. This includes abended, failed, and canceled jobs. (The status display indicates ENDED.) FAILED CC=nnnn The job failed with a FAILCODE of nnnn HELD The schedule or job was held: LATE INTRPTD NOTREQ STARTED SUBMITD AUTO OPER DEAD MAX MUST Due to automatic recovery By the Unicenter CA-Scheduler HOLD command The schedule or job caused a late message to be issued because it: Did not finish by the COMPLETION DEADLINE time Exceeded the MAXIMUM EXECUTION time Did not start by the MUST START BY time. The job was interrupted. The schedule or job is in the inactive queue. The schedule or job is executing. The job has been submitted. 7-12 Unicenter CA-Scheduler User Guide
7.3 Issuing Online Commands in Batch Major Minor Description SUBMFAIL WAIT The job was submitted, but failed. The schedule or job is waiting for: OPSUB PRED RESC START Operator submission (jobs only) A predecessor to be satisfied Defined resources (jobs only) Its early start time. 7.3.3 Some Examples 7.3.3.1 Example 1 The following examples show how you might issue some commands in batch. Suppose you have an online application called NETSCD and when it is shut down, you want to set an indicator that allows a set of backup jobs to begin processing. You can assign a global parameter to this function. Assume a global parameter GLBC4 and assign it a value of NETSCDUP when the system is running, and the value NETSCDWN when the system is not running and backups can be taken. You would use the following transaction in one of the first steps when starting up the NETSCD task. This step would execute the CAJUCMD0 program. SC SET GLBC4=NETSCDUP This means that whenever the NETSCD task is running, the global parameter GLBC4 is set to a value other than NETSCDWN. Now, when the system is shut down, one of the last steps is to set GLBC4 to the value NETSCDWN, which will allow the backup jobs to be started. The transaction for the step that executes the CAJUCMD0 program will be: SC SET GLBC4=NETSCDWN Chapter 7. Techniques 7-13
- 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
- Page 242 and 243: 5.4 What Is Wrong with These Exampl
- Page 245 and 246: Chapter 6. Tips This topic of the m
- Page 247 and 248: 6.1 Commonly Asked Questions 6.1.1.
- Page 249 and 250: 6.1 Commonly Asked Questions Keep i
- Page 251 and 252: 6.1 Commonly Asked Questions 6.1.2.
- Page 253 and 254: 6.1 Commonly Asked Questions To all
- Page 255 and 256: 6.1 Commonly Asked Questions For de
- Page 257 and 258: 6.1 Commonly Asked Questions use of
- Page 259 and 260: 6.1 Commonly Asked Questions 6.1.4
- Page 261 and 262: 6.1 Commonly Asked Questions If the
- Page 263 and 264: 6.1 Commonly Asked Questions Status
- Page 265 and 266: 6.2 Pitfalls predecessor criteria o
- Page 267 and 268: Chapter 7. Techniques This chapter
- Page 269 and 270: 7.1 On-Request Schedules and Jobs 7
- Page 271 and 272: 7.1 On-Request Schedules and Jobs 7
- Page 273 and 274: 7.1 On-Request Schedules and Jobs W
- Page 275 and 276: 7.2 Backlogged Work completes on We
- Page 277: 7.3 Issuing Online Commands in Batc
- Page 281 and 282: 7.3 Issuing Online Commands in Batc
- Page 283 and 284: 7.4 Restart/Recovery of Scheduled J
- Page 285 and 286: 7.5 Multiple CPU Considerations 7.5
- Page 287 and 288: 7.5 Multiple CPU Considerations Nor
- Page 289 and 290: 7.5 Multiple CPU Considerations exe
- Page 291 and 292: 7.5 Multiple CPU Considerations CAJ
- Page 293 and 294: 7.6 NJE Processing In the preceding
- Page 295 and 296: 7.6 NJE Processing 7.6.2.1 NJE Job
- Page 297 and 298: 7.6 NJE Processing 7.6.4 Installati
- Page 299 and 300: 7.6 NJE Processing Status BUSY Mean
- Page 301 and 302: 7.7 Summing Up Prefix PW DM Transac
- Page 303 and 304: Glossary This glossary defines term
- Page 305 and 306: documentation batch command. A comm
- Page 307 and 308: Unicenter CA-Scheduler uses when or
- Page 309 and 310: The payroll department's month-end
- Page 311 and 312: Index Special Characters "Who is lo
- Page 313 and 314: Commands (continued) operator (cont
- Page 315 and 316: F FAIL CODE field 7-16 FAILED queue
- Page 317 and 318: MBR SUBID field 3-65 MCPU installat
- Page 319 and 320: Predecessors (continued) types (con
- Page 321 and 322: Scheduling (continued) jobs 1-5, 5-
- Page 323: User (continued) authority levels 2
7.3 Issuing Online Commands in Batch<br />
Major Minor Description<br />
SUBMFAIL<br />
WAIT<br />
The job was submitted, but failed.<br />
The schedule or job is waiting <strong>for</strong>:<br />
OPSUB<br />
PRED<br />
RESC<br />
START<br />
Operator submission (jobs only)<br />
A predecessor to be satisfied<br />
Defined resources (jobs only)<br />
Its early start time.<br />
7.3.3 Some Examples<br />
7.3.3.1 Example 1<br />
The following examples show how you might issue some commands in batch.<br />
Suppose you have an online application called NETSCD and when it is shut<br />
down, you want to set an indicator that allows a set of backup jobs to begin<br />
processing. You can assign a global parameter to this function. Assume a<br />
global parameter GLBC4 and assign it a value of NETSCDUP when the system<br />
is running, and the value NETSCDWN when the system is not running and<br />
backups can be taken.<br />
You would use the following transaction in one of the first steps when starting<br />
up the NETSCD task. This step would execute the <strong>CA</strong>JUCMD0 program.<br />
SC SET GLBC4=NETSCDUP<br />
This means that whenever the NETSCD task is running, the global parameter<br />
GLBC4 is set to a value other than NETSCDWN.<br />
Now, when the system is shut down, one of the last steps is to set GLBC4 to<br />
the value NETSCDWN, which will allow the backup jobs to be started. The<br />
transaction <strong>for</strong> the step that executes the <strong>CA</strong>JUCMD0 program will be:<br />
SC SET GLBC4=NETSCDWN<br />
Chapter 7. Techniques 7-13
Change language