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 A value of YES on the schedule base record causes Unicenter CA-Scheduler to start that schedule no earlier than the time shown on the Simulated Execution Schedule. If USE SIM TIME = YES on the job base record, Unicenter CA-Scheduler submits that job at the time indicated on the Simulated Execution Schedule. Notice the subtle difference here. The SIMTIME fields on schedule and job records do not override one another because they deal with separate events: when schedules start and when jobs are submitted. Sites that want to schedule jobs using SIMTIME get best results when SIMTIME values on both the schedule and job records are YES. If you set USE SIMTIME=YES on the schedule base record, Unicenter CA-Scheduler ignores any other start times you may have specified for schedules, either on the reason code record or the schedule's base record. If USE SIMTIME = NO, Unicenter CA-Scheduler checks to see what start times you have specified on the schedule's records. 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., 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 production days to hold those jobs. For example, a start time of 031400 holds that schedule until 2 p.m. three production days after that schedule was originally selected. Notice that production days usually do not start at midnight. Instead, they run from one autoscan to the next. The first place Unicenter CA-Scheduler looks for a start time is on the schedule's reason code record (SRC). If you do not specify a start time there that corresponds with the reason the schedule was selected today, Unicenter CA-Scheduler looks to see if you defined an EARLIEST START TIME on the schedule base record. Start times defined on job records are not even looked at until a job's schedule starts. Then Unicenter CA-Scheduler checks to see if you have delayed any jobs by defining start times on job records. Since start time is an important factor in sequencing your workload, Unicenter CA-Scheduler gives you flexibility. For example, a schedule or job may need to start at different times on different days. Unicenter CA-Scheduler allows you to define different reasons for selecting a schedule or job on its criteria record (SCR or JCR). Each reason can cause work to be selected on a different day. Once you have defined reasons on a criteria record, you can specify a different start time for each reason. A schedule's alternate start times are stored on its reason code record (SRC). Likewise, a job's alternate start times are stored on its reason code record (JRC). If a job has no criteria record or it only needs one start time, specify that value as EARLIEST START TIME on the job base record. When Unicenter CA-Scheduler organizes the work to be processed each day, first it considers predecessors. Then it checks start times. If schedules or jobs have the same predecessors and start times, Unicenter CA-Scheduler puts 3-62 Unicenter CA-Scheduler User Guide
3.9 Defining Jobs those with earlier deadlines ahead of the others. Work that has to be finished sooner goes first. You define deadlines in the field called COMPLETION DEADLINE TIME. Schedule deadlines affect how schedules are ordered in the workload. Job deadlines have no impact on the sequencing of schedules and only affect how jobs within a schedule are organized. For information on the role deadlines play in progress notification, see the topics What Happens When Schedules Run Late and What Happens When Jobs Run Late. Finally, Unicenter CA-Scheduler checks one last field when it is 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. Likewise, jobs in the same schedule with the same predecessors, start times, and deadlines are sorted by JOB PRIORTY. 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. Unicenter CA-Scheduler handles jobs within schedules in the same way: jobs with the same values for all these fields are put into alphabetical order in the work queue. The factors determining the order of schedules in the workload are listed following in decreasing order of importance. Sequence By Using On The Schedule Predecessors Criteria language Criteria record Start times Deadline USE SIMTIME = YES EARLY TIMEs or EARLIEST START TIME DEADLINE TIMEs or COMPLETION DEADLINE TIME Base record Base code record Base record Reason code record Base record Priority SCHED PRIORITY Base record Alphabetical order SCHEDULE NAME Base record Factors determining the order of jobs within schedules are listed following in decreasing order of importance. Sequence By Using On The Schedule Predecessors Criteria language Criteria record Start times USE SIMTIME = YES EARLY TIMEs or EARLIEST START TIME Base record Base code record Base record Chapter 3. Maintaining the Database 3-63
- 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 and 118: 3.9 Defining Jobs 3.9.3.3 When Will
- Page 119: 3.9 Defining Jobs The chart precedi
- 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
- Page 169 and 170: 3.14 Summary of Job Maintenance 3.1
3.9 Defining <strong>Job</strong>s<br />
those with earlier deadlines ahead of the others. Work that has to be finished<br />
sooner goes first. You define deadlines in the field called COMPLETION<br />
DEADLINE TIME. Schedule deadlines affect how schedules are ordered in the<br />
workload. <strong>Job</strong> deadlines have no impact on the sequencing of schedules and<br />
only affect how jobs within a schedule are organized. For in<strong>for</strong>mation on the<br />
role deadlines play in progress notification, see the topics What Happens<br />
When Schedules Run Late and What Happens When <strong>Job</strong>s Run Late.<br />
Finally, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> checks one last field when it is 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. Likewise, jobs in the same<br />
schedule with the same predecessors, start times, and deadlines are sorted by<br />
JOB PRIORTY.<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. <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> handles jobs within schedules in<br />
the same way: jobs with the same values <strong>for</strong> all these fields are put into<br />
alphabetical order in the work queue.<br />
The factors determining the order of schedules in the workload are listed<br />
following in decreasing order of importance.<br />
Sequence By Using On The Schedule<br />
Predecessors Criteria language Criteria record<br />
Start times<br />
Deadline<br />
USE SIMTIME = YES<br />
EARLY TIMEs or<br />
EARLIEST START TIME<br />
DEADLINE TIMEs or<br />
COMPLETION DEADLINE<br />
TIME<br />
Base record<br />
Base code record<br />
Base record<br />
Reason code record<br />
Base record<br />
Priority SCHED PRIORITY Base record<br />
Alphabetical<br />
order<br />
SCHEDULE NAME<br />
Base record<br />
Factors determining the order of jobs within schedules are listed following in<br />
decreasing order of importance.<br />
Sequence By Using On The Schedule<br />
Predecessors Criteria language Criteria record<br />
Start times<br />
USE SIMTIME = YES<br />
EARLY TIMEs or<br />
EARLIEST START TIME<br />
Base record<br />
Base code record<br />
Base record<br />
Chapter 3. Maintaining the Database 3-63
Change language