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 3.9.3.9 How Do You Phase Unicenter CA-Scheduler into Production? Fields on both the schedule and job base records allow you to implement Unicenter CA-Scheduler in stages: ■ ■ AUTO SELECT on the schedule base record LIBRARY TYPE AUTO SELECT on the schedule base record controls whether Unicenter CA-Scheduler evaluates this schedule automatically during autoscan. When AUTO SELECT = NO, this schedule is skipped and these jobs are not included in the daily workload. That is exactly what you want to happen while you are developing definitions for a schedule's jobs. Once you have verified those definitions using the Analyze and simulation reports, set AUTO SELECT = YES to include this schedule in the evaluation process that occurs at every autoscan. Although this schedule may already include production work, you can let Unicenter CA-Scheduler take control of the selection of this work by specifying AUTO SELECT = YES. The next implementation phase permits you to monitor Unicenter CA-Scheduler's operation while it submits dummy JCL for each of your jobs. This gives you three important capabilities: ■ ■ ■ When you are first implementing Unicenter CA-Scheduler, you can run the product in parallel with your normal production. Without affecting your regular operation, you can verify that Unicenter CA-Scheduler is processing your workload as planned. Even experienced Unicenter CA-Scheduler sites use this technique to prepare for implementing new applications. TESTLIB enables you to define and test definitions for applications that are not yet ready to go into production. You can check your selection criteria and verify the order in which jobs will run before they have even been handed over to production. You can also test the effect of abended and failed jobs by using TESTLIB to cause those conditions for specific jobs. To initiate this phase, change AUTO SELECT to YES on the schedule base record and set LIBRARY TYPE to TESTLIB. Remember that if LIBRARY TYPE is defined at the job level, it overrides the value you specify on that job's schedule base record. You can quickly verify what library type applies to your jobs by checking that value on the Job Directory panel. When Unicenter CA-Scheduler sees that LIBRARY TYPE = TESTLIB, it constructs the JCL to run a simple Computer Associates utility program: CAJUTSTA. You can use TESTPARM=testparm on individual jobs to cause the test program to abend, to pass a nonzero completion code, and to have it wait for a number of seconds. Thus, you can test the effect of abending and failing jobs on the rest of the schedule. 3-70 Unicenter CA-Scheduler User Guide
3.9 Defining Jobs When you are ready to automate the selection process, set AUTO SELECT = YES and identify where the JCL for these jobs is stored using the fields described in the topic What JCL Does Unicenter CA-Scheduler Submit For CPU Jobs. 3.9.3.10 What Job Fields are Used for Simulation? Without actually executing your jobs, simulation produces reports showing: ■ ■ ■ ■ ■ ■ Which jobs would be selected What resources would be required When and where each job would be processed How heavily each device would be utilized Which jobs would be late Which jobs would carryover to the next day Because simulation is such an effective planning tool, take the time to supply the data needed to run simulation. First, indicate which CPU these jobs run on. See the topic Which CPU Should Jobs Run On for instructions showing how that is done. Then specify the other data required to run simulations. AVERAGE TIME allows you to override the computed average run times for this job derived from historical data. If you specify a value here, Unicenter CA-Scheduler uses that time for simulation. The value reflects how much time elapsed between when the job starts and ends. If you do not specify a value here, Unicenter CA-Scheduler averages the elapsed times for the last seven days the job ran. You can change the value for AVERAGE TIME to determine the impact of production changes before they actually happen. First, run simulation with Unicenter CA-Scheduler's computed value for AVERAGE TIME. Then key in a different value and rerun simulation. By comparing the reports, you will be able to see the impact of such a change on your production workload. Unicenter CA-Scheduler uses POWER CLASS to assign jobs to partitions on the simulation reports. POWER CLASS should correspond to the value of the CLASS parameter on JOB statements submitted to POWER (a single character, 0-9 or A-Z). Since that field occurs on both the schedule and job base record, you only need to specify POWER CLASS for a job if the value on its schedule base record is not appropriate for this job. To refine the accuracy of your simulation runs, define the resources each job requires on the job resource record (JRR). This information is not required to run simulation. However, unless resources have been defined, you will not be able to USE SIMTIME to start schedules and jobs. Instruction on how that is done are found in the topic Defining A Job's Resource Record. Chapter 3. Maintaining the Database 3-71
- 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
- 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: 3.9 Defining Jobs ■ ■ ■ ■ O
- 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
- 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
3.9 Defining <strong>Job</strong>s<br />
When you are ready to automate the selection process, set AUTO SELECT =<br />
YES and identify where the JCL <strong>for</strong> these jobs is stored using the fields<br />
described in the topic What JCL Does <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> Submit For<br />
CPU <strong>Job</strong>s.<br />
3.9.3.10 What <strong>Job</strong> Fields are Used <strong>for</strong> Simulation?<br />
Without actually executing your jobs, simulation produces reports showing:<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
Which jobs would be selected<br />
What resources would be required<br />
When and where each job would be processed<br />
How heavily each device would be utilized<br />
Which jobs would be late<br />
Which jobs would carryover to the next day<br />
Because simulation is such an effective planning tool, take the time to supply<br />
the data needed to run simulation. First, indicate which CPU these jobs run<br />
on. See the topic Which CPU Should <strong>Job</strong>s Run On <strong>for</strong> instructions showing<br />
how that is done. Then specify the other data required to run simulations.<br />
AVERAGE TIME allows you to override the computed average run times <strong>for</strong><br />
this job derived from historical data. If you specify a value here, <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> uses that time <strong>for</strong> simulation. The value reflects how much time<br />
elapsed between when the job starts and ends. If you do not specify a value<br />
here, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> averages the elapsed times <strong>for</strong> the last seven<br />
days the job ran.<br />
You can change the value <strong>for</strong> AVERAGE TIME to determine the impact of<br />
production changes be<strong>for</strong>e they actually happen. First, run simulation with<br />
<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>'s computed value <strong>for</strong> AVERAGE TIME. Then key in a<br />
different value and rerun simulation. By comparing the reports, you will be<br />
able to see the impact of such a change on your production workload.<br />
<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> uses POWER CLASS to assign jobs to partitions on<br />
the simulation reports. POWER CLASS should correspond to the value of the<br />
CLASS parameter on JOB statements submitted to POWER (a single character,<br />
0-9 or A-Z). Since that field occurs on both the schedule and job base record,<br />
you only need to specify POWER CLASS <strong>for</strong> a job if the value on its schedule<br />
base record is not appropriate <strong>for</strong> this job.<br />
To refine the accuracy of your simulation runs, define the resources each job<br />
requires on the job resource record (JRR). This in<strong>for</strong>mation is not required to<br />
run simulation. However, unless resources have been defined, you will not be<br />
able to USE SIMTIME to start schedules and jobs. Instruction on how that is<br />
done are found in the topic Defining A <strong>Job</strong>'s Resource Record.<br />
Chapter 3. Maintaining the Database 3-71