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.9 Defining Jobs SCHD-JCRE DEF C= J=IH7D2 JN=1 ST=4 S=BACKUP CA-Scheduler ===> RANGE=1-72 1...+....1....+....2....+....3....+....4....+....5....+....6....+....7... MON OR /EVERY MONDAY OR / 1 TUE OR /EVERY TUESDAY OR / 2 WED OR /EVERY WEDNESDAY OR / 3 THU /EVERY THURSDAY / 4 5 6 7 8 9 1 11 12 13 14 15 16 17 18 19 1...+....1....+....2....+....3....+....4....+....5....+....6....+....7... Next, define this job to run Monday through Thursday. Type in the criteria statement shown preceding to define four reasons for selecting this job. Although it really does not matter where on this panel you enter your criteria, we recommend you type each reason for selecting a job on a separate line so that it is easier to see which reasons here correspond with fields on the job's reason code record. If there is more than one reason for selecting a job, each reason ends with OR (except the last one, of course). Note: Multiple ORs can be grouped into a single reason code by placing parentheses around this reason. (See the chapter "Criteria Language" for more details.) When you write criteria, you can embed comments anywhere by using /* as a beginning delimiter and */ as an ending delimiter. These delimiters can appear on different lines if the comment is longer than one line. The preceding criteria statement will cause Unicenter CA-Scheduler to select this job less frequently than the rest of the schedule. That means Unicenter CA-Scheduler selects the BACKUP schedule every day. On Monday through Thursday, Unicenter CA-Scheduler puts this job in the daily workload. 3-78 Unicenter CA-Scheduler User Guide

3.9 Defining Jobs The criteria statement you just defined contains no predecessors. Therefore, this job will be submitted when: ■ ■ ■ ■ The schedule's early start time is reached The schedule's predecessor conditions have been met The job's start time is reached and The job's defined resources are available Note: Predecessors in job records are not evaluated until its schedule has started and the job's early start time has been reached. For complete information on coding criteria statements, see the chapter "Criteria Language." To save this criteria record and leave this panel, type FILE in the command input area. Otherwise, you could leave the panel without saving this criteria record by typing QUIT. All of the editor commands are in the appendix "Editor Commands" in the Unicenter CA-Scheduler Reference Guide. The FILE command causes Unicenter CA-Scheduler to immediately create that job's criteria record. After you press Enter, Unicenter CA-Scheduler displays the following panel, which confirms that record has been created: SCHD-UTIL SCHDUTIL OUTPUT Scheduler ===> MASTER - WR CONNECT : 4 DEFINE JCR S=BACKUP,NAME=IH7D2,JNO=1,ST=4,CRI=' MON OR TUE OR WED OR THU' CACU18I JCR IH7D2 HAS BEEN ADDED PF1=HELP To advance to the next panel, press Enter. 3.9.4.2 Defining a Job's Reason Code Record If you defined a criteria record for a job, you may also want to use the options available on a job's reason code record. That record allows you to define different values for the following fields: ■ ■ ■ ■ ■ AVERAGE TIME EARLIEST START TIME MUST START BY TIME COMPLETION DEADLINE TIME MAXIMUM EXECUTION TIME A job reason code record works just like a schedule's reason code record: Chapter 3. Maintaining the Database 3-79

3.9 Defining <strong>Job</strong>s<br />

<br />

<br />

SCHD-JCRE DEF C= J=IH7D2 JN=1 ST=4 S=BACKUP <strong>CA</strong>-<strong>Scheduler</strong><br />

===><br />

RANGE=1-72<br />

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...<br />

MON OR /EVERY MONDAY OR / 1<br />

TUE OR /EVERY TUESDAY OR / 2<br />

WED OR /EVERY WEDNESDAY OR / 3<br />

THU /EVERY THURSDAY / 4<br />

5<br />

6<br />

7<br />

8<br />

9<br />

1<br />

11<br />

12<br />

13<br />

14<br />

15<br />

16<br />

17<br />

18<br />

19<br />

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...<br />

<br />

<br />

Next, define this job to run Monday through Thursday. Type in the criteria<br />

statement shown preceding to define four reasons <strong>for</strong> selecting this job.<br />

Although it really does not matter where on this panel you enter your criteria,<br />

we recommend you type each reason <strong>for</strong> selecting a job on a separate line so<br />

that it is easier to see which reasons here correspond with fields on the job's<br />

reason code record. If there is more than one reason <strong>for</strong> selecting a job, each<br />

reason ends with OR (except the last one, of course).<br />

Note: Multiple ORs can be grouped into a single reason code by placing<br />

parentheses around this reason. (See the chapter "Criteria Language" <strong>for</strong><br />

more details.)<br />

When you write criteria, you can embed comments anywhere by using /* as a<br />

beginning delimiter and */ as an ending delimiter. These delimiters can appear<br />

on different lines if the comment is longer than one line.<br />

The preceding criteria statement will cause <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> to select<br />

this job less frequently than the rest of the schedule. That means <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> selects the BACKUP schedule every day. On Monday through<br />

Thursday, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> puts this job in the daily workload.<br />

3-78 <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!