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.2 Defining Optional Schedule Records SCHD-UTIL SCHDUTIL OUTPUT CA-SCHEDULER ===> MASTER - WR CONNECT : 4 DEFINE SRC NAME=BACKUP,ERLY1=22,ERLY2=23,MAX1=1, MAX2=3 CACU18I SRC BACKUP HAS BEEN ADDED PF1=HELP Use of reason codes provides you with tremendous scheduling flexibility. To advance to the next panel, press Enter. 3.2.3 Defining a Schedule Information Record All the schedule records you have defined so far contain information that affects how Unicenter CA-Scheduler automates production at your site. Usually, this record does not. A schedule's information record is purely for your use. It stores descriptive information about this schedule that helps your staff wrap up the work Unicenter CA-Scheduler began for you. A schedule's information record only affects processing if your site has implemented an optional simulation user exit. If so, the EXITPARM defined here is passed to that user exit during simulation. SCHD-SIR INFO DEFINITION CA-SCHEDULER ===> MASTER - WR CONNECT : 4 SCHEDULE NAME : backup PROTOTYPE SCHEDULE NAME : DESCRIPTION COMMENT EXITPARM : copies data sets to tape : rerun if this abends FORM : QUANTITY : NOTIFY : j smith RESPONSIBILITY: j smith VERIFY : SPECIFICATION : DESTINATIONS-1: tape 2:library 3: 4: 5: 6: 7: 8: DELIVERABLES 1: backup tapes 2: 3: 4: 5: 6: 7: 8: RECS= SBR: Y SCR: Y SRC: Y SIR: N SMR: N PF1=HELP SCHEDULE NAME The only required value in an information record. The other fields are optional and most allow you to input anything you feel is appropriate. These field names are intentionally general so you can record the information you think will be most useful. 3-26 Unicenter CA-Scheduler User Guide
3.2 Defining Optional Schedule Records EXITPARM VERIFY EXITPARM adjusts the default class or default average processing time of all jobs in this schedule during simulation. Unicenter CA-Scheduler passes this value of up to 16 bytes to a user exit. Requires a specific response. Your choices are to leave the field blank, or type in YES or NO. Use this field for anything you want by setting up your own standard for this field. Next, create the information record shown preceding. As you tab from field to field, type in the data displayed on the panel preceding. After you have input that information, you are ready to create the information record. After you have filled in the panel, press Enter to save the information record for that schedule. Unicenter CA-Scheduler confirms that it stored that information by displaying the following panel: SCHD-UTIL SCHDUTIL OUTPUT CA-SCHEDULER ===> MASTER - WR CONNECT : 4 DEFINE SIR NAME=BACKUP,DESC='COPIES DATA SETS TO TAPE', COMMENT='RERUN IF THIS ABENDS',NOTIFY='J SMITH', RESP='J SMITH',DEST1='TAPE',DEST2='LIBRARY', DEL1='BACKUP TAPES' CACU18I SIR BACKUP HAS BEEN ADDED PF1=HELP To view the next panel, press Enter. That displays the panel that defines the last optional schedule record. 3.2.4 Defining a Schedule Message Record The last optional schedule record helps implement Unicenter CA-Scheduler's message capability by notifying users of a schedule's progress. Unicenter CA-Scheduler is prepared to notify users of four events concerning schedules: ■ ■ ■ ■ When schedules start When they end When they are late When they run too long Chapter 3. Maintaining the Database 3-27
- 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 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: 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 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
3.2 Defining Optional Schedule Records<br />
<br />
SCHD-UTIL SCHDUTIL OUTPUT <strong>CA</strong>-SCHEDULER<br />
===> MASTER - WR<br />
CONNECT : 4<br />
<br />
DEFINE SRC NAME=BACKUP,ERLY1=22,ERLY2=23,MAX1=1,<br />
MAX2=3<br />
<strong>CA</strong>CU18I SRC BACKUP HAS BEEN ADDED<br />
<br />
PF1=HELP<br />
<br />
Use of reason codes provides you with tremendous scheduling flexibility. To<br />
advance to the next panel, press Enter.<br />
3.2.3 Defining a Schedule In<strong>for</strong>mation Record<br />
All the schedule records you have defined so far contain in<strong>for</strong>mation that<br />
affects how <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> automates production at your site.<br />
Usually, this record does not. A schedule's in<strong>for</strong>mation record is purely <strong>for</strong><br />
your use. It stores descriptive in<strong>for</strong>mation about this schedule that helps your<br />
staff wrap up the work <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> began <strong>for</strong> you.<br />
A schedule's in<strong>for</strong>mation record only affects processing if your site has<br />
implemented an optional simulation user exit. If so, the EXITPARM defined<br />
here is passed to that user exit during simulation.<br />
<br />
SCHD-SIR INFO DEFINITION <strong>CA</strong>-SCHEDULER<br />
===> MASTER - WR<br />
CONNECT : 4<br />
<br />
SCHEDULE NAME : backup PROTOTYPE SCHEDULE NAME :<br />
DESCRIPTION<br />
COMMENT<br />
EXITPARM<br />
: copies data sets to tape<br />
: rerun if this abends<br />
FORM : QUANTITY :<br />
NOTIFY : j smith RESPONSIBILITY: j smith<br />
VERIFY :<br />
SPECIFI<strong>CA</strong>TION :<br />
DESTINATIONS-1: tape 2:library 3: 4:<br />
5: 6: 7: 8:<br />
DELIVERABLES<br />
1: backup tapes 2: 3: 4:<br />
5: 6: 7: 8:<br />
<br />
RECS= SBR: Y SCR: Y SRC: Y SIR: N SMR: N<br />
PF1=HELP<br />
<br />
SCHEDULE NAME<br />
The only required value in an in<strong>for</strong>mation record.<br />
The other fields are optional and most allow you to<br />
input anything you feel is appropriate. These field<br />
names are intentionally general so you can record the<br />
in<strong>for</strong>mation you think will be most useful.<br />
3-26 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>