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
5.4 What Is Wrong with These Examples? After JOBB in SCHED01 is selected, only these predecessors are left for evaluation: (JOBA AND GBLB01=YES) When JOBA is not in the day's workload, Unicenter CA-Scheduler knows that it cannot be a predecessor. Example 6 Criteria for job JOBB: MON OR TUE OR WED OR THU OR FRI OR (SAT AND PRED JOBA) The intent is that JOBB would run Monday through Saturday, but only on Saturday if JOBA completed sometime since last Saturday (for example, it may be that JOBA only runs on Fridays). The rule is that keyword-defined explicit predecessors apply across all selection criteria. Consequently, JOBB will wait for JOBA every time JOBB is selected (even on Monday, Tuesday, and so forth). To accomplish this, you have to set up JOBB as two separate jobs: JOBB-01 and JOBB-02. Notice how the criteria for JOBB-01 has been simplified following. The correct way of coding this criteria statement is: Criteria for the first job JOBB-01: WEEK-DAY Criteria for the second job JOBB-02: SAT AND PRED JOBA 5-28 Unicenter CA-Scheduler User Guide
5.5 Summing Up 5.5 Summing Up Evaluate criteria statements twice: once to determine selection criteria and again to identify predecessor conditions. When coding a job in the criteria language, always qualify it with its schedule name. Use the SCD keyword before a schedule name to identify it as such. Selection Predecessors Calendars Datetables A job will only be evaluated for selection and eligible for today's workload if its schedule is selected or eligible for today's workload. A schedule is considered eligible for selection if the only reason it was not selected is because it was defined with AUTO SELECT=NO. The NOT keyword only applies to selection. Every job or schedule listed in a criteria statement is a predecessor if it is also in or eligible to be in the day's production. Whether those jobs or schedules are part of the reason for selection does not matter. Unicenter CA-Scheduler observes ORs used with all keyword-defined predecessors except PRED, meaning NJE,VSE, DSN, GDG, and GBLxnn. A criteria statement like NOT JOBA defines JOBA as a predecessor. If jobs or schedules are predecessors, Unicenter CA-Scheduler waits for them to complete unless you precede their names with the keyword START. Define daily, weekly, and monthly calendars for selecting schedules and jobs. When using calendars, only the calendar name determines selection. Define three years' worth of datetables for each unique datetable name. Each year being accessed must have a datetable for the year before and after it. Chapter 5. Criteria Language 5-29
- Page 192 and 193: 4.2 Displaying Status The last two
- 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
- 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 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
5.5 Summing Up<br />
5.5 Summing Up<br />
Evaluate criteria statements twice: once to determine selection criteria and<br />
again to identify predecessor conditions. When coding a job in the criteria<br />
language, always qualify it with its schedule name. Use the SCD keyword<br />
be<strong>for</strong>e a schedule name to identify it as such.<br />
Selection<br />
Predecessors<br />
Calendars<br />
Datetables<br />
A job will only be evaluated <strong>for</strong> selection and eligible <strong>for</strong><br />
today's workload if its schedule is selected or eligible <strong>for</strong><br />
today's workload. A schedule is considered eligible <strong>for</strong><br />
selection if the only reason it was not selected is because it<br />
was defined with AUTO SELECT=NO.<br />
The NOT keyword only applies to selection.<br />
Every job or schedule listed in a criteria statement is a<br />
predecessor if it is also in or eligible to be in the day's<br />
production. Whether those jobs or schedules are part of the<br />
reason <strong>for</strong> selection does not matter.<br />
<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> observes ORs used with all<br />
keyword-defined predecessors except PRED, meaning<br />
NJE,<strong>VSE</strong>, DSN, GDG, and GBLxnn.<br />
A criteria statement like NOT JOBA defines JOBA as a<br />
predecessor.<br />
If jobs or schedules are predecessors, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />
waits <strong>for</strong> them to complete unless you precede their names<br />
with the keyword START.<br />
Define daily, weekly, and monthly calendars <strong>for</strong> selecting<br />
schedules and jobs. When using calendars, only the calendar<br />
name determines selection.<br />
Define three years' worth of datetables <strong>for</strong> each unique<br />
datetable name. Each year being accessed must have a<br />
datetable <strong>for</strong> the year be<strong>for</strong>e and after it.<br />
Chapter 5. Criteria Language 5-29