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 On-Request Schedules and Jobs 7.1.1 Discussion This topic discusses on-request schedules and jobs and gives you many examples of criteria language. On-request schedules and jobs are ones that are selected every day, and placed in an inactive queue, in case they are needed. They remain in an INACTIVE status until they are activated by an operator command which means that you cannot determine in advance whether the schedule or job will be needed on any particular day. You define an on-request schedule or job using REQUESTED, a Gregorian calendar reserved word, in its selection criteria. When the autoscan process runs, all REQUESTED schedules and jobs are selected along with their successors and placed in Unicenter CA-Scheduler's tracking file in an inactive queue. The only way they can be removed from the inactive queue is using the operator command REQUEST or SREQ. When removed from the inactive queue, they are placed in the active queue and will then be handled as normally selected jobs. An important difference between the REQUEST and SREQ commands is that REQUEST also places the successor schedules and jobs in the active queue. The SREQ command handles successors differently: SREQ will not activate a successor if it involves other requested jobs. A successor of an SREQed schedule or job will not be moved to the active queue if: ■ ■ The successor's criteria statement contains the keyword REQUESTED or That successor is also the successor of some other requested job in the inactive queue All schedules and jobs that have not been requested by the next autoscan are purged from Unicenter CA-Scheduler's tracking file, regardless of which BACKLOG values they had defined. There is a guideline you should follow when using the REQUESTED keyword: To ensure that simulation produces reason codes that match those produced by Unicenter CA-Scheduler, specify REQUESTED after job and schedule names in selection criteria whenever possible. 7-2 Unicenter CA-Scheduler User Guide
7.1 On-Request Schedules and Jobs 7.1.2 Criteria Language Subtleties 7.1.2.1 Example 1 The best way to explain these subtleties is with examples. Each example assumes that the jobs described are all contained in the same schedule. Although you should always specify schedule names with job names in criteria statements, they are omitted in the examples following to keep things simple. Job JOBA JOBB JOBC Criteria REQUESTED JOBA JOBB 7.1.2.2 Example 2 In the preceding example, all three jobs will be placed in the inactive queue every day. Job JOBA Criteria MON AND REQUESTED JOBA will be placed in the inactive queue every Monday. 7.1.2.3 Example 3 Job JOBA Criteria MON OR REQUESTED 7.1.2.4 Example 4 The preceding example follows the same rules as MON when selected on Monday and treated as a normal job (meaning that on Mondays, it is placed in the active queue and it does not have to be requested). Any other day, it will be treated as a requested job. Job JOBA JOBA1 JOBB Criteria REQUESTED None JOBA OR JOBA1 Chapter 7. Techniques 7-3
- 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
- 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: Chapter 7. Techniques This chapter
- 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 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
7.1 On-Request Schedules and <strong>Job</strong>s<br />
7.1.2 Criteria Language Subtleties<br />
7.1.2.1 Example 1<br />
The best way to explain these subtleties is with examples. Each example<br />
assumes that the jobs described are all contained in the same schedule.<br />
Although you should always specify schedule names with job names in criteria<br />
statements, they are omitted in the examples following to keep things simple.<br />
<strong>Job</strong><br />
JOBA<br />
JOBB<br />
JOBC<br />
Criteria<br />
REQUESTED<br />
JOBA<br />
JOBB<br />
7.1.2.2 Example 2<br />
In the preceding example, all three jobs will be placed in the inactive queue<br />
every day.<br />
<strong>Job</strong><br />
JOBA<br />
Criteria<br />
MON AND REQUESTED<br />
JOBA will be placed in the inactive queue every Monday.<br />
7.1.2.3 Example 3<br />
<strong>Job</strong><br />
JOBA<br />
Criteria<br />
MON OR REQUESTED<br />
7.1.2.4 Example 4<br />
The preceding example follows the same rules as MON when selected on<br />
Monday and treated as a normal job (meaning that on Mondays, it is placed in<br />
the active queue and it does not have to be requested). Any other day, it will<br />
be treated as a requested job.<br />
<strong>Job</strong><br />
JOBA<br />
JOBA1<br />
JOBB<br />
Criteria<br />
REQUESTED<br />
None<br />
JOBA OR JOBA1<br />
Chapter 7. Techniques 7-3
Change language