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 SCHD-JMR MESSAGE DEFINITION Scheduler ===> MASTER - WR CONNECT : 4 JOB NAME : IH7D2 PROTOTYPE JOB: JNO: STN: JOB NUMBER : 1 PROTOTYPE JOB IN SCHEDULE : STATION ID : 4 SCHEDULE NAME : BACKUP SEND ALL MESSAGES TO : SEND START MESSAGES TO : SEND END MESSAGES TO : SEND LATE MESSAGES TO : operator SEND ABEND MESSAGES TO : operator SEND FAIL MESSAGES TO : operator SEND INTERRUPT MESSAGE TO: RECS= JBR: N JCR: N JRC: N JIR: N JMR: N JRR: N JNR: N PF1=HELP You can initiate every kind of job progress reporting by filling in one field on the job message record. If that is the only field you fill in on this record, all job-related messages will go to that ID. Suppose you entered YOURID as a value for SEND ALL MESSAGES. If you fill in other fields on this record, it affects which messages go to YOURID. YOURID will get only those messages not routed elsewhere. If you really want YOURID to get all messages, be sure to include YOURID in every userid list you specify on this panel. You can list up to four userids separated by commas in any of these fields. To send any kind of message to the master console, specify OPERATOR as one of the userids. You can also specify MAILBOX as one of the userids, and the messages will be sent to a common mailbox where they can be viewed using the Reporting Facility panel. The panel preceding creates a job message record that sends abend, fail, and late messages to the master console. Try creating that record on your own by tabbing to these fields and typing the value OPERATOR. Unicenter CA-Scheduler needs to know more to produce some of these messages. The chart following tells you what fields need to be completed to activate each kind of message. For These Messages Specify On The Start messages SEND START MESSAGES JMR End messages SEND END MESSAGES JMR 3-84 Unicenter CA-Scheduler User Guide
3.9 Defining Jobs For These Messages Specify On The Late messages -SEND LATE MESSAGES and -MUST START BY TIME MUST TIMEs -COMPLETION DEADLINE TIME or DEADLINE TIMEs -MAXIMUM EXECUTION TIME or MAXIMUM TIMEs JMR JBR JRC JBR JRC JBR JRC Abend messages SEND ABEND MESSAGES JMR Fail messages SEND FAIL MESSAGES JMR Interrupt messages INTERRUPT and SEND INTERRUPT MESSAGE JBR JMR You can send a message when this job misses its deadline because you already defined deadlines on the job's reason code record. Then press Enter to save the job's message record. Unicenter CA-Scheduler responds by displaying the following message: SCHD-UTIL SCHDUTIL OUTPUT Scheduler ===> MASTER - WR CONNECT : 4 DEFINE JMR NAME=IH7D2,JNO=1,STATION=4,SCHEDULE=BACKUP, LATEMSG=(OPERATOR),ABENDMSG=(OPERATOR),FAILMSG=(OPERATOR) CACU18I JMR IH7D2 HAS BEEN ADDED PF1=HELP To view the next panel, press Enter. 3.9.4.5 Defining a Job Resource Record The job resource record provides the information needed to run simulations. Most of the fields show what types of devices your job requires. Unicenter CA-Scheduler even maintains several key fields itself using data. To explore this record in more detail, enter the displayed data in the appropriate fields: Chapter 3. Maintaining the Database 3-85
- 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
- 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: 3.9 Defining Jobs DESTINATIONS and
- 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
- Page 178 and 179: 4.2 Displaying Status Schedules and
- Page 180 and 181: 4.2 Displaying Status The table fol
- Page 182 and 183: 4.2 Displaying Status To Restrict T
- Page 184 and 185: 4.2 Displaying Status 4.2.4.1 Defau
- Page 186 and 187: 4.2 Displaying Status SCHD-CP SCHE
- Page 188 and 189: 4.2 Displaying Status If the schedu
- Page 190 and 191: 4.2 Displaying Status or backlogged
3.9 Defining <strong>Job</strong>s<br />
<br />
SCHD-JMR MESSAGE DEFINITION <strong>Scheduler</strong><br />
===> MASTER - WR<br />
CONNECT : 4<br />
<br />
JOB NAME : IH7D2 PROTOTYPE JOB: JNO: STN:<br />
JOB NUMBER : 1 PROTOTYPE JOB IN SCHEDULE :<br />
STATION ID : 4<br />
SCHEDULE NAME : BACKUP<br />
SEND ALL MESSAGES TO :<br />
SEND START MESSAGES TO :<br />
SEND END MESSAGES TO :<br />
SEND LATE MESSAGES TO : operator<br />
SEND ABEND MESSAGES TO : operator<br />
SEND FAIL MESSAGES TO : operator<br />
SEND INTERRUPT MESSAGE TO:<br />
<br />
RECS= JBR: N JCR: N JRC: N JIR: N JMR: N JRR: N JNR: N<br />
PF1=HELP<br />
<br />
You can initiate every kind of job progress reporting by filling in one field on<br />
the job message record. If that is the only field you fill in on this record, all<br />
job-related messages will go to that ID. Suppose you entered YOURID as a<br />
value <strong>for</strong> SEND ALL MESSAGES. If you fill in other fields on this record, it<br />
affects which messages go to YOURID. YOURID will get only those messages<br />
not routed elsewhere. If you really want YOURID to get all messages, be sure<br />
to include YOURID in every userid list you specify on this panel.<br />
You can list up to four userids separated by commas in any of these fields. To<br />
send any kind of message to the master console, specify OPERATOR as one of<br />
the userids.<br />
You can also specify MAILBOX as one of the userids, and the messages will be<br />
sent to a common mailbox where they can be viewed using the Reporting<br />
Facility panel.<br />
The panel preceding creates a job message record that sends abend, fail, and<br />
late messages to the master console. Try creating that record on your own by<br />
tabbing to these fields and typing the value OPERATOR.<br />
<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> needs to know more to produce some of these<br />
messages. The chart following tells you what fields need to be completed to<br />
activate each kind of message.<br />
For These Messages Specify On The<br />
Start messages SEND START MESSAGES JMR<br />
End messages SEND END MESSAGES JMR<br />
3-84 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>