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.1 Defining Schedules If USE SIMTIME = NO, Unicenter CA-Scheduler checks to see what start times you have specified on the schedule record. You specify the earliest possible time a schedule can start using a 24-hour clock. For example, an early time of 1400 allows a schedule to start no earlier than 2 p.m. in the afternoon. But what if that schedule should not start until some day in the future? Unicenter CA-Scheduler also allows you to specify start times with a prefix showing how many days to delay the start of those jobs. For example, a start time of 031400 delays the start of that schedule until 2 p.m., three days after that schedule was originally selected. If USE SIMTIME=NO, Unicenter CA-Scheduler checks to see if a schedule's reason code record contains start times. Since start time is an important factor in sequencing your workload, Unicenter CA-Scheduler gives you flexibility. For example, a schedule may need to start at different times on different days. This is not a problem because Unicenter CA-Scheduler allows you to define different reasons for selecting a schedule on its criteria record (SCR). Each reason can cause that schedule to be selected on a different day. Once you have defined reasons on the SCR, you can specify a different start time for each reason. A schedule's alternate start times are stored on its reason code record (SRC). The last place Unicenter CA-Scheduler looks for a start time is EARLIEST START TIME. If you do not specify a start time anywhere, Unicenter CA-Scheduler only delays starting this schedule until its predecessor conditions are satisfied. When Unicenter CA-Scheduler organizes the work to be processed each day, first it considers each schedule's predecessors. Then it checks start times. If several schedules have the same predecessors and start times, Unicenter CA-Scheduler puts those with earlier deadlines ahead of the others. Work that has to be finished sooner goes first. You define deadlines in fields called DEADLINE TIME on the reason code record or COMPLETION DEADLINE TIME on the schedule base record. Finally, Unicenter CA-Scheduler checks one last field when it's organizing the workload. Schedules with the same predecessors, start times, and deadlines are sorted by SCHED PRIORITY: schedules with the highest priority go first. Priorities range from a high of 01 to a low of 99. If, after checking all these fields, Unicenter CA-Scheduler finds a group of schedules with equivalent values in all these fields, it lines up those schedules in alphabetical order. The chart following summarizes how Unicenter CA-Scheduler organizes its workload. Sequence By Using On The Predecessors Criteria language Criteria record 3-12 Unicenter CA-Scheduler User Guide
3.1 Defining Schedules Sequence By Using On The Start times Deadline USE SIMTIME = YES EARLY TIMEs EARLIEST START TIME DEADLINE TIMEs COMPLETION DEADLINE TIME Base record Reason code record Base record Reason code record Base record Priority SCHED PRIORITY Base record Alphabetical order SCHEDULE NAME Base record What if Unicenter CA-Scheduler does not complete some schedules in the day's workload? Any jobs that are running when the next autoscan occurs are always automatically backlogged, but what happens to jobs that have not started yet? BACKLOG fields control what happens if a schedule's jobs do not run on the day they were selected. BACKLOG occurs on both schedule and job base records. The value defined for a schedule applies to all jobs in that schedule unless you override it by specifying a different value on a job base record. Jobs that have BACKLOG=YES on their job base record (or default to BACKLOG=YES on the schedule's base record) will always be backlogged if they have not completed or been canceled by the next autoscan. Jobs with BACKLOG=NO on their job base record (or default to BACKLOG=NO on their schedule's base record) will be removed from the workload if they are still waiting at the next autoscan. If that schedule would also be selected tomorrow, the second set of jobs is added to the workload after the backlogged schedule has completed and been purged. Chapter 3. Maintaining the Database 3-13
- Page 20 and 21: 1.3 Additional Features ■ Which j
- Page 22 and 23: 1.4 Summing Up 1.4 Summing Up The f
- Page 24 and 25: 2.1 Getting Started 2.1 Getting Sta
- Page 26 and 27: 2.1 Getting Started SCHD-MM MAIN
- Page 28 and 29: 2.1 Getting Started 2.1.4 Logging O
- Page 30 and 31: 2.2 Maintaining Stations SCHD-WM S
- Page 32 and 33: 2.2 Maintaining Stations SCHD-UTIL
- Page 34 and 35: 2.2 Maintaining Stations To submit
- Page 36 and 37: 2.2 Maintaining Stations SCHD-WM S
- Page 38 and 39: 2.2 Maintaining Stations SCHD-WM S
- Page 40 and 41: 2.2 Maintaining Stations SCHD-WD S
- Page 42 and 43: 2.3 Maintaining User Records 2.3 Ma
- Page 44 and 45: 2.3 Maintaining User Records SCHD-
- Page 46 and 47: 2.3 Maintaining User Records To All
- Page 48 and 49: 2.3 Maintaining User Records Unicen
- Page 50 and 51: 2.3 Maintaining User Records Users
- Page 52 and 53: 2.3 Maintaining User Records SCHD-
- Page 54 and 55: 2.3 Maintaining User Records Option
- Page 56 and 57: 2.3 Maintaining User Records If use
- Page 59 and 60: Chapter 3. Maintaining the Database
- Page 61 and 62: 3.1 Defining Schedules ■ ■ ■
- Page 63 and 64: 3.1 Defining Schedules AUTO SELECT
- Page 65 and 66: 3.1 Defining Schedules 3.1.3 Checki
- Page 67 and 68: 3.1 Defining Schedules Option Purpo
- Page 69: 3.1 Defining Schedules 3.1.4.2 When
- 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 and 118: 3.9 Defining Jobs 3.9.3.3 When Will
- Page 119 and 120: 3.9 Defining Jobs The chart precedi
3.1 Defining Schedules<br />
If USE SIMTIME = NO, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> checks to see what start times<br />
you have specified on the schedule record. You specify the earliest possible<br />
time a schedule can start using a 24-hour clock. For example, an early time of<br />
1400 allows a schedule to start no earlier than 2 p.m. in the afternoon. But<br />
what if that schedule should not start until some day in the future? <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> also allows you to specify start times with a prefix showing how<br />
many days to delay the start of those jobs. For example, a start time of 031400<br />
delays the start of that schedule until 2 p.m., three days after that schedule<br />
was originally selected.<br />
If USE SIMTIME=NO, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> checks to see if a schedule's<br />
reason code record contains start times. Since start time is an important factor<br />
in sequencing your workload, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> gives you flexibility.<br />
For example, a schedule may need to start at different times on different days.<br />
This is not a problem because <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> allows you to define<br />
different reasons <strong>for</strong> selecting a schedule on its criteria record (SCR). Each<br />
reason can cause that schedule to be selected on a different day. Once you<br />
have defined reasons on the SCR, you can specify a different start time <strong>for</strong><br />
each reason. A schedule's alternate start times are stored on its reason code<br />
record (SRC).<br />
The last place <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> looks <strong>for</strong> a start time is EARLIEST<br />
START TIME. If you do not specify a start time anywhere, <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> only delays starting this schedule until its predecessor<br />
conditions are satisfied.<br />
When <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> organizes the work to be processed each day,<br />
first it considers each schedule's predecessors. Then it checks start times. If<br />
several schedules have the same predecessors and start times, <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> puts those with earlier deadlines ahead of the others. Work that<br />
has to be finished sooner goes first. You define deadlines in fields called<br />
DEADLINE TIME on the reason code record or COMPLETION DEADLINE<br />
TIME on the schedule base record.<br />
Finally, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> checks one last field when it's organizing the<br />
workload. Schedules with the same predecessors, start times, and deadlines are<br />
sorted by SCHED PRIORITY: schedules with the highest priority go first.<br />
Priorities range from a high of 01 to a low of 99.<br />
If, after checking all these fields, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> finds a group of<br />
schedules with equivalent values in all these fields, it lines up those schedules<br />
in alphabetical order. The chart following summarizes how <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> organizes its workload.<br />
Sequence By Using On The<br />
Predecessors Criteria language Criteria record<br />
3-12 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>