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
4.11 Summing Up This Command Affects Jobs/ Schedules This way TALTER S,J Temporarily changes values defined in the database for just this execution. Before using any of these commands, refer to the chapter "Controlling Schedules and Jobs" in the Unicenter CA-Scheduler Reference Guide Part 1 for complete command descriptions. 4-42 Unicenter CA-Scheduler User Guide
Chapter 5. Criteria Language The criteria language consists of a criteria vocabulary and a set of calendar mechanisms used to construct a reason, or set of reasons, for selecting a schedule or job for execution and for establishing its predecessors. For example, if SCHEDA is to run every Monday and every Thursday, the selection criteria associated with this schedule is MON OR THU. This example uses criteria vocabulary that refers to a processing period when selecting a schedule. Several different types of processing periods can be used: ■ ■ ■ ■ ■ ■ ■ ■ ■ Day of week (as preceding) Week of month Day in cycle Week in cycle Workday Relative day Accounting day of month Holiday Negative day of month (nn day from the end of a period) Another condition that can cause selection of a schedule or job would be another schedule or job being selected. For example, to select JOBB if JOBA was selected, the criteria associated with JOBB is JOBA. Previously, using the criteria vocabulary to select schedules or jobs was discussed, but the criteria vocabulary is also used for defining predecessors. Predecessors are conditions that have to be met before a schedule or job is allowed to start. Other terms used for predecessor are prerequisite and dependency. Predecessors can be the starting or ending of other schedules or jobs, the closing of an output data set, a nonscheduled VSE job, and other items like these. Any predecessor can be defined as occurring on the day the schedule or job is selected or as having occurred on a prior day. This will be discussed in more detail later through the use of examples. Chapter 5. Criteria Language 5-1
- Page 163 and 164: 3.13 Automatic Console Replies for
- Page 165 and 166: 3.13 Automatic Console Replies for
- Page 167 and 168: 3.13 Automatic Console Replies for
- Page 169 and 170: 3.14 Summary of Job Maintenance 3.1
- Page 171: 3.14 Summary of Job Maintenance To
- Page 174 and 175: 4.1 Online Monitoring Panel 4.1 Onl
- Page 176 and 177: 4.1 Online Monitoring Panel This ch
- Page 178 and 179: 4.2 Displaying Status Schedules and
- Page 180 and 181: 4.2 Displaying Status The table fol
- Page 182 and 183: 4.2 Displaying Status To Restrict T
- Page 184 and 185: 4.2 Displaying Status 4.2.4.1 Defau
- Page 186 and 187: 4.2 Displaying Status SCHD-CP SCHE
- Page 188 and 189: 4.2 Displaying Status If the schedu
- Page 190 and 191: 4.2 Displaying Status or backlogged
- 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 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 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
4.11 Summing Up<br />
This<br />
Command<br />
Affects <strong>Job</strong>s/<br />
Schedules<br />
This way<br />
TALTER S,J Temporarily changes values defined in<br />
the database <strong>for</strong> just this execution.<br />
Be<strong>for</strong>e using any of these commands, refer to the chapter "Controlling<br />
Schedules and <strong>Job</strong>s" in the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> Reference <strong>Guide</strong> Part 1 <strong>for</strong><br />
complete command descriptions.<br />
4-42 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>
Change language