03.03.2015 Views

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

■<br />

■<br />

■<br />

It is only valid if a criteria record exists <strong>for</strong> that job and selection is not<br />

accomplished by a calendar.<br />

It allows you to define up to 16 different values <strong>for</strong> certain fields, one <strong>for</strong><br />

each reason why this job could be selected.<br />

<strong>Scheduler</strong> checks to see the reason why a job was selected, and then<br />

applies the corresponding values when processing the job that day.<br />

The only difference is that a job's reason code record applies to a specific job<br />

while a schedule's reason code record applies to that schedule. A job's values<br />

do not default to its schedule's values. Type the displayed values under MUST<br />

TIME LIST and MAXIMUM TIME LIST.<br />

<br />

<br />

SCHD-JRC REASONS DEFINITION <strong>Scheduler</strong><br />

===> MASTER - WR<br />

CONNECT : 4<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 />

AVG TIME LIST:<br />

1 2 3 4 5 6 7 8<br />

9 1 11 12 13 14 15 16<br />

EARLY TIME LIST:<br />

1 2 3 4 5 6 7 8<br />

9 1 11 12 13 14 15 16<br />

MUST TIME LIST:<br />

1 2215 2 2315 3 2315 4 2315 5 6 7 8<br />

9 1 11 12 13 14 15 16<br />

DEADLINE TIME LIST:<br />

1 2 3 4 5 6 7 8<br />

9 1 11 12 13 14 15 16<br />

MAXIMUM TIME LIST:<br />

1 15 2 1 3 1 4 1 5 6 7 8<br />

9 1 11 12 13 14 15 16<br />

RECS= JBR: Y JCR: Y JRC: N JIR: N JMR: N JRR: N JNR: N<br />

PF1=HELP<br />

<br />

<br />

The Reasons Definition panel allows you to specify up to 16 different values<br />

<strong>for</strong> these five fields, which have meanings similar to fields found on the job's<br />

base record. <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> matches these values with the reasons<br />

defined on the job's criteria record: the first values here apply to the first<br />

reason the job was selected, and so on. Our example shows different values<br />

defined <strong>for</strong> two fields. How does this relate to the job's criteria statement and<br />

the schedule's reason code record?<br />

■<br />

■<br />

■<br />

On Mondays, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> will issue warning messages if this<br />

job does not start by 10:15 p.m. or runs longer than 15 minutes.<br />

On other days, messages are issued if the job hasn't started by 11:15 p.m.<br />

or it takes longer than 10 minutes to run.<br />

The schedule's reason code record sets the default early start times <strong>for</strong> all<br />

the jobs in this schedule based upon the reason why the schedule was<br />

selected. None of a schedule's non-CPU jobs can be started and none of its<br />

CPU jobs can be submitted until the schedule's start time has been<br />

reached.<br />

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