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.1 Defining Schedules<br />

3.1.4.2 When Will a Schedule's <strong>Job</strong>s Actually Run?<br />

As <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> selects the day's workload, it organizes the work,<br />

grouping each schedule's jobs together, but it does not line schedules up in the<br />

order they are selected. Instead, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> allows you to control<br />

the work sequence with several schedule parameters:<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

SCR predecessors<br />

USE SIMTIME<br />

EARLIEST START TIME<br />

SRC start times<br />

COMPLETION DEADLINE TIME<br />

SCHD PRIORITY<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 any jobs in that schedule. Predecessors can be a variety of<br />

events such as<br />

■<br />

■<br />

■<br />

■<br />

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

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

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

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

When schedules must run in a certain order, define schedules as predecessors<br />

to one another using the schedule criteria record (SCR). See the chapter<br />

"Criteria Language" <strong>for</strong> instructions on how that is done.<br />

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

day, the first factor it considers is each schedule's predecessors. Then<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> compares the start times <strong>for</strong> schedules, putting those<br />

that can start earliest ahead of ones that start later. Schedules without<br />

predecessors and start times go to the top of the list because nothing is<br />

delaying them, so they start right after autoscan. SCHD PRIORITY is the last<br />

factor <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> considers when organizing the workload and<br />

only serves to sort schedules that have equivalent values <strong>for</strong> all the other<br />

factors.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> gives you three ways of specifying when jobs start.<br />

To see which method you chose, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> checks the value of<br />

USE SIMTIME. A value of YES causes <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> to start that<br />

schedule at the time shown on the Simulated Execution Schedule.<br />

If you set USE SIMTIME=YES, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> ignores any other start<br />

times you may have specified. <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> sites that have defined<br />

their resources in great detail and run the vast majority of their production<br />

load under <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> control could set USE SIMTIME=YES. The<br />

accuracy of their history data and resource definitions would result in<br />

simulations that project optimal start times <strong>for</strong> schedules. However, most<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> sites leave USE SIMTIME=NO.<br />

Chapter 3. Maintaining the Database 3-11

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

Saved successfully!

Ooh no, something went wrong!