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
3.9 Defining Jobs Defining predecessors forces Unicenter CA-Scheduler to witness a specific event before starting AUTO-STARTed non-CPU jobs or submitting CPU jobs. Predecessors can be a variety of events: ■ ■ ■ ■ ■ The start or end of another schedule or job The close of an output data set or output generation data group A user-defined event that you can control using a global parameter The normal completion of a job that isn't controlled by Unicenter CA-Scheduler An event that occurred sometime in the past Defining predecessors for schedules forces Unicenter CA-Scheduler to witness a specific event before evaluating any jobs in that schedule. You can also define predecessors for individual jobs. If both a schedule and its jobs have predecessors: ■ ■ None of the schedule's jobs will be evaluated until the schedule's predecessors are satisfied and the schedule starts. Once the schedule's predecessors are met, other factors such as start times determine whether the job is ready to be submitted once its predecessors are satisfied. Note: Defining predecessors for jobs does not override a schedule's predecessors: instead, predecessors are cumulative. When jobs must run in a certain order, define predecessors for either schedules or jobs. Be careful deciding what that predecessor should be: check what days your predecessor is selected. For example, suppose your job's predecessor isn't eligible to be selected on the same day your job is. If a predecessor is not in the day's workload, Unicenter CA-Scheduler ignores it: your job runs without waiting for the predecessor. This feature makes writing criteria statements easier. See the chapter "Criteria Language" for instructions on how that is done. When Unicenter CA-Scheduler lines up work to be processed during the day, the first factor it considers is predecessors. Then Unicenter CA-Scheduler compares start times, putting schedules that can start earliest ahead of ones that start later. Unicenter CA-Scheduler orders jobs within schedules in the same way: jobs that can start earlier go ahead of jobs from the same schedule that have later start times. Schedules without predecessors and start times go to the top of the list because nothing is delaying them from starting. Likewise, jobs without predecessors and start times are the first jobs listed for each schedule. 3-60 Unicenter CA-Scheduler User Guide
3.9 Defining Jobs The chart preceding illustrates how Unicenter CA-Scheduler sequences jobs. Schedule A is first because A has no predecessors. Schedule B is ahead of C because B has no start time. Now look at Schedule A's jobs to see why they are sequenced in this order. Job A1 is first because it has no predecessors and no start time. Since A3 has predecessors, A2 goes ahead of it. Now look at job start times in Schedule B. B1 has no start time so it goes ahead of B2. B2 is next because it can start earlier than B3. B4 is last because only that job has predecessors in addition to the predecessors defined for the schedule. Even though B4 has an earlier start time, its predecessors put it at the end of Schedule B. Now look at Schedule C to see how schedule and job start times interact. Schedule C starts at 9 a.m. Job C1 does not have a start time, but its schedule does. Therefore, C1 will not start until 9 a.m. What about C2? Its start time is 6 a.m., but this schedule does not start until three hours later. Therefore, C2 cannot start before 9 a.m. even if you give it an earlier start time. Note: Job start times do not override specified schedule start times. Instead, they let you postpone running jobs after a schedule has started. Unicenter CA-Scheduler gives you three ways of specifying when jobs start. To see which method you chose, Unicenter CA-Scheduler checks the values of USE SIMTIME. SIMTIME is only used at sites with extensive Unicenter CA-Scheduler experience. Such sites have defined their resources in great detail and automated the vast majority of their workload using Unicenter CA-Scheduler. As a result, they have refined simulation to such a degree that it accurately reflects their daily operation. In fact, their simulation runs are so accurate that those sites can rely on simulation data to determine when schedules can start and jobs can be submitted. USE SIMTIME defaults to NO. Only sites using Unicenter CA-Scheduler's most advanced features choose to implement SIMTIME as their start time. Chapter 3. Maintaining the Database 3-61
- Page 67 and 68: 3.1 Defining Schedules Option Purpo
- Page 69 and 70: 3.1 Defining Schedules 3.1.4.2 When
- Page 71 and 72: 3.1 Defining Schedules Sequence By
- Page 73 and 74: 3.1 Defining Schedules If your site
- Page 75 and 76: 3.1 Defining Schedules A Value Of U
- Page 77 and 78: 3.2 Defining Optional Schedule Reco
- Page 79 and 80: 3.2 Defining Optional Schedule Reco
- Page 81 and 82: 3.2 Defining Optional Schedule Reco
- Page 83 and 84: 3.2 Defining Optional Schedule Reco
- Page 85 and 86: 3.2 Defining Optional Schedule Reco
- Page 87 and 88: 3.3 Copying Schedules 3.3 Copying S
- Page 89 and 90: 3.3 Copying Schedules To Copy A Sch
- Page 91 and 92: 3.4 Displaying Schedules SCHD-SU S
- Page 93 and 94: 3.4 Displaying Schedules PRESS ENTE
- Page 95 and 96: 3.5 Deleting Schedules SCHD-SD SC
- Page 97 and 98: 3.5 Deleting Schedules If you are n
- Page 99 and 100: 3.6 Analyzing Schedules SCHD-UTIL
- Page 101 and 102: 3.6 Analyzing Schedules Unicenter C
- Page 103 and 104: 3.7 Automatic Console Replies for S
- Page 105 and 106: 3.7 Automatic Console Replies for S
- Page 107 and 108: 3.7 Automatic Console Replies for S
- Page 109 and 110: 3.8 Summary of Schedule Maintenance
- Page 111 and 112: 3.9 Defining Jobs 3.9 Defining Jobs
- Page 113 and 114: 3.9 Defining Jobs SCHD-JU JOB DEF
- Page 115 and 116: 3.9 Defining Jobs SCHD-JM JOB MAIN
- Page 117: 3.9 Defining Jobs 3.9.3.3 When Will
- Page 121 and 122: 3.9 Defining Jobs those with earlie
- Page 123 and 124: 3.9 Defining Jobs 3.9.3.5 What JCL
- Page 125 and 126: 3.9 Defining Jobs If You Have multi
- Page 127 and 128: 3.9 Defining Jobs ■ ■ ■ ■ O
- Page 129 and 130: 3.9 Defining Jobs When you are read
- Page 131 and 132: 3.9 Defining Jobs If You Want Notif
- Page 133 and 134: 3.9 Defining Jobs If You Want To Se
- Page 135 and 136: 3.9 Defining Jobs The Job Criteria
- Page 137 and 138: 3.9 Defining Jobs The criteria stat
- Page 139 and 140: 3.9 Defining Jobs ■ MAXIMUM TIMEs
- Page 141 and 142: 3.9 Defining Jobs DESTINATIONS and
- Page 143 and 144: 3.9 Defining Jobs For These Message
- Page 145 and 146: 3.9 Defining Jobs To Separate All J
- Page 147 and 148: 3.9 Defining Jobs 3.9.4.6 Defining
- Page 149 and 150: 3.10 Displaying and Updating a Job
- Page 151 and 152: 3.10 Displaying and Updating a Job
- Page 153 and 154: 3.10 Displaying and Updating a Job
- Page 155 and 156: 3.11 Deleting Job Records 3.11 Dele
- Page 157 and 158: 3.11 Deleting Job Records SCHD-JM
- Page 159 and 160: 3.12 Analyzing Jobs 3.12 Analyzing
- Page 161 and 162: 3.12 Analyzing Jobs To display a fu
- 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
3.9 Defining <strong>Job</strong>s<br />
The chart preceding illustrates how <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> sequences jobs.<br />
Schedule A is first because A has no predecessors. Schedule B is ahead of C<br />
because B has no start time. Now look at Schedule A's jobs to see why they are<br />
sequenced in this order. <strong>Job</strong> A1 is first because it has no predecessors and no<br />
start time. Since A3 has predecessors, A2 goes ahead of it.<br />
Now look at job start times in Schedule B. B1 has no start time so it goes<br />
ahead of B2. B2 is next because it can start earlier than B3. B4 is last because<br />
only that job has predecessors in addition to the predecessors defined <strong>for</strong> the<br />
schedule. Even though B4 has an earlier start time, its predecessors put it at<br />
the end of Schedule B.<br />
Now look at Schedule C to see how schedule and job start times interact.<br />
Schedule C starts at 9 a.m. <strong>Job</strong> C1 does not have a start time, but its schedule<br />
does. There<strong>for</strong>e, C1 will not start until 9 a.m. What about C2? Its start time is<br />
6 a.m., but this schedule does not start until three hours later. There<strong>for</strong>e, C2<br />
cannot start be<strong>for</strong>e 9 a.m. even if you give it an earlier start time.<br />
Note: <strong>Job</strong> start times do not override specified schedule start times. Instead,<br />
they let you postpone running jobs after a schedule has started.<br />
<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> gives you three ways of specifying when jobs start.<br />
To see which method you chose, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> checks the values of<br />
USE SIMTIME. SIMTIME is only used at sites with extensive <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> experience. Such sites have defined their resources in great<br />
detail and automated the vast majority of their workload using <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong>. As a result, they have refined simulation to such a degree that<br />
it accurately reflects their daily operation. In fact, their simulation runs are so<br />
accurate that those sites can rely on simulation data to determine when<br />
schedules can start and jobs can be submitted. USE SIMTIME defaults to NO.<br />
Only sites using <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>'s most advanced features choose to<br />
implement SIMTIME as their start time.<br />
Chapter 3. Maintaining the Database 3-61
Change language