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

supportcontent.ca.com
from supportcontent.ca.com More from this publisher
03.03.2015 Views

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

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>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!