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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Defining predecessors <strong>for</strong>ces <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> to witness a specific<br />

event be<strong>for</strong>e starting AUTO-STARTed non-CPU jobs or submitting CPU jobs.<br />

Predecessors can be a variety of events:<br />

■<br />

■<br />

■<br />

■<br />

■<br />

The start or end of another schedule or job<br />

The close of an output data set or output generation data group<br />

A user-defined event that you can control using a global parameter<br />

The normal completion of a job that isn't controlled by <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong><br />

An event that occurred sometime in the past<br />

Defining predecessors <strong>for</strong> schedules <strong>for</strong>ces <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> to witness<br />

a specific event be<strong>for</strong>e evaluating any jobs in that schedule. You can also<br />

define predecessors <strong>for</strong> individual jobs. If both a schedule and its jobs have<br />

predecessors:<br />

■<br />

■<br />

None of the schedule's jobs will be evaluated until the schedule's<br />

predecessors are satisfied and the schedule starts.<br />

Once the schedule's predecessors are met, other factors such as start times<br />

determine whether the job is ready to be submitted once its predecessors<br />

are satisfied.<br />

Note: Defining predecessors <strong>for</strong> jobs does not override a schedule's<br />

predecessors: instead, predecessors are cumulative.<br />

When jobs must run in a certain order, define predecessors <strong>for</strong> either schedules<br />

or jobs. Be careful deciding what that predecessor should be: check what days<br />

your predecessor is selected. For example, suppose your job's predecessor isn't<br />

eligible to be selected on the same day your job is. If a predecessor is not in<br />

the day's workload, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> ignores it: your job runs without<br />

waiting <strong>for</strong> the predecessor. This feature makes writing criteria statements<br />

easier. See the chapter "Criteria Language" <strong>for</strong> instructions on how that is<br />

done.<br />

When <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> lines up work to be processed during the day,<br />

the first factor it considers is predecessors. Then <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />

compares start times, putting schedules that can start earliest ahead of ones<br />

that start later. <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> orders jobs within schedules in the<br />

same way: jobs that can start earlier go ahead of jobs from the same schedule<br />

that have later start times.<br />

Schedules without predecessors and start times go to the top of the list because<br />

nothing is delaying them from starting. Likewise, jobs without predecessors<br />

and start times are the first jobs listed <strong>for</strong> each schedule.<br />

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