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.1 On-Request Schedules and Jobs 7.1.2.5 Example 5 In the preceding example, all jobs will be selected. JOBA and JOBB will be placed in the inactive queue. JOBB is placed there because JOBA is the first predecessor specified and it is a requested job. The ordering of these predecessors is important as you will see with the next example. JOBA1 will be run whenever its conditions allow (if there are none, it will start immediately). JOBB will always wait for JOBA1 (that is, you could request JOBB without requesting JOBA). If JOBA is requested (with the REQUEST or SREQ command), JOBB will automatically be requested and will wait for both JOBA and JOBA1. If no requests are made, JOBA and JOBB will be purged from the tracking file at the next autoscan. Job JOBA JOBA1 JOBB Criteria REQUESTED None JOBA1 OR JOBA 7.1.2.6 Example 6 The preceding example is the same as the one previous except for the order of the predecessors on JOBB. All three jobs will be selected, but only JOBA is placed on the inactive queue. This is because JOBB got selected because of JOBA1, which is selected whenever the schedule is selected. JOBB will always wait for JOBA1, but will only wait for JOBA if JOBA is requested (using the operator command REQUEST or SREQ) before JOBA1 completes. If JOBA is not requested, it will be purged from the tracking file at the next autoscan. Job JOBA JOBB Criteria REQUESTED JOBA AND REQUESTED Both JOBA and JOBB will be placed in the inactive queue at autoscan time. 7-4 Unicenter CA-Scheduler User Guide
7.1 On-Request Schedules and Jobs 7.1.2.7 Example 7 When the operator command REQ J N=JOBA is issued, both jobs (JOBA and JOBB) will be moved to the active queue. When the operator command SREQ J N=JOBA is issued, only job JOBA will be moved to the active queue. JOBB will not be moved since it has the criteria AND REQUESTED that must be satisfied. It is not satisfied using the SREQ operator command with its predecessor JOBA. To move JOBB to the active queue, in this case, use the REQUEST or SREQ command. Job JOBA JOBB Criteria REQUESTED MON OR JOBA 7.1.2.8 Example 8 On Mondays, JOBB will be added to the active queue and will not wait for JOBA unless it is also in the active queue. That is, JOBA will not be considered a predecessor of JOBB unless JOBA is requested with the REQUEST or SREQ command before JOBB is submitted. Once JOBA and JOBB are both in the active queue, Unicenter CA-Scheduler will not submit JOBB until JOBA has completed. Job JOBA JOBA1 JOBB JOBC Criteria REQUESTED REQUESTED JOBA OR JOBA1 JOBA All four jobs will be placed in the inactive queue at autoscan time. Chapter 7. Techniques 7-5
- 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
- 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: 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 and 278: 7.3 Issuing Online Commands in Batc
- 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
7.1 On-Request Schedules and <strong>Job</strong>s<br />
7.1.2.5 Example 5<br />
In the preceding example, all jobs will be selected. JOBA and JOBB will be<br />
placed in the inactive queue. JOBB is placed there because JOBA is the first<br />
predecessor specified and it is a requested job. The ordering of these<br />
predecessors is important as you will see with the next example.<br />
JOBA1 will be run whenever its conditions allow (if there are none, it will start<br />
immediately).<br />
JOBB will always wait <strong>for</strong> JOBA1 (that is, you could request JOBB without<br />
requesting JOBA). If JOBA is requested (with the REQUEST or SREQ<br />
command), JOBB will automatically be requested and will wait <strong>for</strong> both JOBA<br />
and JOBA1.<br />
If no requests are made, JOBA and JOBB will be purged from the tracking file<br />
at the next autoscan.<br />
<strong>Job</strong><br />
JOBA<br />
JOBA1<br />
JOBB<br />
Criteria<br />
REQUESTED<br />
None<br />
JOBA1 OR JOBA<br />
7.1.2.6 Example 6<br />
The preceding example is the same as the one previous except <strong>for</strong> the order of<br />
the predecessors on JOBB. All three jobs will be selected, but only JOBA is<br />
placed on the inactive queue. This is because JOBB got selected because of<br />
JOBA1, which is selected whenever the schedule is selected.<br />
JOBB will always wait <strong>for</strong> JOBA1, but will only wait <strong>for</strong> JOBA if JOBA is<br />
requested (using the operator command REQUEST or SREQ) be<strong>for</strong>e JOBA1<br />
completes.<br />
If JOBA is not requested, it will be purged from the tracking file at the next<br />
autoscan.<br />
<strong>Job</strong><br />
JOBA<br />
JOBB<br />
Criteria<br />
REQUESTED<br />
JOBA AND REQUESTED<br />
Both JOBA and JOBB will be placed in the inactive queue at autoscan time.<br />
7-4 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>
Change language