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
6.1 Commonly Asked Questions 6.1 Commonly Asked Questions This topic consists of a series of questions that are commonly asked. The following table lists the topic category with associated questions which are answered following the table. Topic Startup Tasks Maintaining The Database Analyzing The Database Daily Processing Question When should autoscan be performed? What is the general standard for numbering stations? Should I use datetables or calendars? When should I define a new datetable versus a new cycle in an existing datetable? How should I organize my schedules? Is there a fast way to add data to the database? When should a job be staged? When is a job submitted? What are global parameters and when are they used? How can I run a job like an edit check repeatedly until its output is correct? How and when can I display documentation automatically? What are my options when a job abends? How can I prevent predecessor loops? When should I run forecasts? When should I run simulation? How do I plan when to run a new application? How do I verify a new application? Is there a way that I can create my own reports? From where can I issue Unicenter CA-Scheduler operator commands? What is the difference between FORCE, SUBMIT, RERUN, RUN, ADD, REQUEST, and SREQ? When is the PRED flag reset? What happens if there was a system crash? 6.1.1 Startup Tasks Commonly asked questions concerning startup tasks follow. 6-2 Unicenter CA-Scheduler User Guide
6.1 Commonly Asked Questions 6.1.1.1 When Should Autoscan Be Performed? Autoscan is the daily process that purges completed jobs from the Scheduler tracking file, backlogs schedules and jobs, if appropriate, and selects the day's workload. Scheduler scans the database, analyzing the selection criteria and placing the selected schedules and jobs onto the tracking file. If your production normally starts at 16:00 and runs during the night with everything completing by 07:00 or 08:00, then autoscan should be run at 08:00 or shortly after that. Run autoscan at a time when your machine load is at a low point. Notice the VSE jobs that are running will not go to the end of job until autoscan completes. This ensures that the Unicenter CA-Scheduler monitor will not miss events such as database close, VSE job ends, scheduler job ends, and so forth. Running autoscan this way gives the production control area a chance to get everything ready for the day's workload, which includes JCL changes, control statement changes, data entry work, last-minute changes, and the like. 6.1.1.2 What Is the General Standard for Numbering Stations? Normally, stations are set up as follows: 20 Data entry 39 JCL staging 40 CPU processing Station 20 Data entry Jobs start at their early start time if you specify AUTO START=YES (as long as their predecessors and resources are satisfied). However, you always have to manually post these data entry jobs when they have ended. Station 39 JCL staging Jobs must be manually posted as ENDED (using the COMPLETE command) before a CPU job with the same name will be submitted. If you specify that the station 39 job is to be automatically started (AUTO START=YES), it will be started at its early start time as long as its predecessors and resources are satisfied. Station 40 CPU processing Jobs will be started when the early start times are met, all predecessor conditions are fulfilled, and resources are available. CPU job processing is automatic unless you override it. Chapter 6. Tips 6-3
- 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 242 and 243: 5.4 What Is Wrong with These Exampl
- Page 245: Chapter 6. Tips This topic of the m
- 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
- 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
6.1 Commonly Asked Questions<br />
6.1.1.1 When Should Autoscan Be Per<strong>for</strong>med?<br />
Autoscan is the daily process that purges completed jobs from the <strong>Scheduler</strong><br />
tracking file, backlogs schedules and jobs, if appropriate, and selects the day's<br />
workload. <strong>Scheduler</strong> scans the database, analyzing the selection criteria and<br />
placing the selected schedules and jobs onto the tracking file.<br />
If your production normally starts at 16:00 and runs during the night with<br />
everything completing by 07:00 or 08:00, then autoscan should be run at 08:00<br />
or shortly after that. Run autoscan at a time when your machine load is at a<br />
low point.<br />
Notice the <strong>VSE</strong> jobs that are running will not go to the end of job until<br />
autoscan completes. This ensures that the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> monitor will<br />
not miss events such as database close, <strong>VSE</strong> job ends, scheduler job ends, and<br />
so <strong>for</strong>th.<br />
Running autoscan this way gives the production control area a chance to get<br />
everything ready <strong>for</strong> the day's workload, which includes JCL changes, control<br />
statement changes, data entry work, last-minute changes, and the like.<br />
6.1.1.2 What Is the General Standard <strong>for</strong> Numbering Stations?<br />
Normally, stations are set up as follows:<br />
20 Data entry<br />
39 JCL staging<br />
40 CPU processing<br />
Station 20 Data entry<br />
<strong>Job</strong>s start at their early start time if you specify AUTO<br />
START=YES (as long as their predecessors and resources are<br />
satisfied). However, you always have to manually post these<br />
data entry jobs when they have ended.<br />
Station 39 JCL staging<br />
<strong>Job</strong>s must be manually posted as ENDED (using the<br />
COMPLETE command) be<strong>for</strong>e a CPU job with the same name<br />
will be submitted. If you specify that the station 39 job is to be<br />
automatically started (AUTO START=YES), it will be started<br />
at its early start time as long as its predecessors and resources<br />
are satisfied.<br />
Station 40 CPU processing<br />
<strong>Job</strong>s will be started when the early start times are met, all<br />
predecessor conditions are fulfilled, and resources are<br />
available. CPU job processing is automatic unless you override<br />
it.<br />
Chapter 6. Tips 6-3
Change language