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 7.3 Issuing Online Commands in Batch A utility program (CAJUCMD0) is provided with Unicenter CA-Scheduler that allows you to: ■ ■ ■ ■ ■ Send operator messages to system console Issue Unicenter CA-Scheduler operator commands Issue VM commands (if you are running under VM) Issue POWER commands Issue CICS CEMT commands or start user transactions 7.3.1 Transaction Format When you combine the facility with some language flexibility, you have considerable power. For example, you could test the condition code of a step in the middle of a job and based on its setting cause some other job or schedule to be released to run. Or if a particular job was submitted before this job, you could place some other job on hold. There are a whole set of status conditions that you can check. These are described later. A more detailed discussion on the format and use of this facility exists in the chapter "Unicenter CA-Scheduler Commands in Batch Mode" in the Unicenter CA-Scheduler Reference Guide Part 1. There are six types of transactions, you have to tell the CAJUCMD0 program which type you are describing which you do by prefixing each transaction with a two-digit code as follows: Prefix MO SC CP PW CI DM Transaction Type Send the following text to the operator console. Issue the following Unicenter CA-Scheduler operator command, which can include the conditional batch IF statement. Issue the following VM command. Issue POWER commands. Issue CICS Transactions. Issue commands stored in the documentation library. 7-10 Unicenter CA-Scheduler User Guide
7.3 Issuing Online Commands in Batch The preceding commands can be executed conditionally based upon the setting of a global parameter or the status of a schedule or job. This introduces the SC transaction that is used with the IF statement. The IF statement can even have AND, OR, and NOT keywords. For example: Transaction: SC IF JOBA INTRPTD SC STATUS S=PAYSCHD Read as: The job that is executing CAJUCMD0 right now wants to determine if the job JOBA is in an interrupted status. If it is, Unicenter CA-Scheduler will print the status of the schedule PAYSCHD and all its jobs. The following describes using the NOT keyword. Transaction: SC IF JOBA NOT COMPLETE SC HOLD J N=JOBB Read as: 7.3.2 Status Checking The job that is executing CAJUCMD0 right now wants to determine whether or not JOBA completed. If it has not, Unicenter CA-Scheduler will place JOBB in HELD status. In the previous examples, the portion of the IF statement that reads JOBA INTRPTD and JOBA NOT COMPLETE is called a condition. There can be more than one condition in an IF statement. In this case, they would be separated by an AND or an OR keyword. If the condition pertains to a schedule or job, the right-hand part of the condition is the status to check against. If you are looking at a global, the right-hand part is the value of the global you want to check. There are two levels of status codes. The major level is a code such as INTRPTD or COMPLETE (as in the previous examples). This is termed the major status code. There are some major status codes that can be optionally qualified with a minor status code. An example of a major status code with a minor status code would be WAIT PRED. WAIT is the major status code and PRED is the minor status code. One example is asking if a schedule or job is in a WAIT status for predecessors. Another example is WAIT START, which is asking if a schedule or job is waiting for its early start time to be met. Chapter 7. Techniques 7-11
- 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
- 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: 7.2 Backlogged Work completes on We
- Page 279 and 280: 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 />
The preceding commands can be executed conditionally based upon the setting<br />
of a global parameter or the status of a schedule or job. This introduces the SC<br />
transaction that is used with the IF statement. The IF statement can even have<br />
AND, OR, and NOT keywords. For example:<br />
Transaction:<br />
SC IF JOBA INTRPTD SC STATUS S=PAYSCHD<br />
Read as:<br />
The job that is executing <strong>CA</strong>JUCMD0 right now wants to determine if the job<br />
JOBA is in an interrupted status. If it is, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> will print the<br />
status of the schedule PAYSCHD and all its jobs.<br />
The following describes using the NOT keyword.<br />
Transaction:<br />
SC IF JOBA NOT COMPLETE SC HOLD J N=JOBB<br />
Read as:<br />
7.3.2 Status Checking<br />
The job that is executing <strong>CA</strong>JUCMD0 right now wants to determine whether<br />
or not JOBA completed. If it has not, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> will place JOBB<br />
in HELD status.<br />
In the previous examples, the portion of the IF statement that reads JOBA<br />
INTRPTD and JOBA NOT COMPLETE is called a condition. There can be<br />
more than one condition in an IF statement. In this case, they would be<br />
separated by an AND or an OR keyword. If the condition pertains to a<br />
schedule or job, the right-hand part of the condition is the status to check<br />
against. If you are looking at a global, the right-hand part is the value of the<br />
global you want to check.<br />
There are two levels of status codes. The major level is a code such as<br />
INTRPTD or COMPLETE (as in the previous examples). This is termed the<br />
major status code. There are some major status codes that can be optionally<br />
qualified with a minor status code. An example of a major status code with a<br />
minor status code would be WAIT PRED. WAIT is the major status code and<br />
PRED is the minor status code. One example is asking if a schedule or job is in<br />
a WAIT status <strong>for</strong> predecessors. Another example is WAIT START, which is<br />
asking if a schedule or job is waiting <strong>for</strong> its early start time to be met.<br />
Chapter 7. Techniques 7-11