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.2 Defining Optional Schedule Records<br />

A review of what the criteria statement SCD DBUPDATE OR DAILY does<br />

follows. The OR without parentheses defines two reasons why this schedule<br />

can be selected. Each reason will be examined independently:<br />

■<br />

■<br />

This schedule is selected whenever the schedule named DBUPDATE is<br />

selected, and on those days, the completion of DBUPDATE is a<br />

predecessor to the backup schedule. All DBUPDATE jobs in the workload<br />

must finish be<strong>for</strong>e any backup jobs can begin.<br />

OR DAILY causes <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> to select the backup schedule<br />

whenever DBUPDATE is not selected. On those days, this schedule has no<br />

predecessors.<br />

That means <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> selects the backup schedule every day.<br />

And on days when DBUPDATE is selected, DBUPDATE is a predecessor to<br />

BACKUP.<br />

Does the order in that criteria statement matter? Would the statement<br />

DAILY OR SCD DBUPDATE<br />

yield the same result? Both statements cause the backup schedule to run on the<br />

same days with the same predecessor. But there is a subtle difference<br />

involving the reasons schedules are selected. Suppose DBUPDATE runs on<br />

Mondays, Wednesdays and Fridays. Making DAILY the first reason in the<br />

criteria statement means this schedule is always selected <strong>for</strong> that reason, but<br />

putting DAILY last<br />

(SCD DBUPDATE OR DAILY)<br />

means that schedule sometimes is selected <strong>for</strong> the second reason.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> has an optional record that allows you to control<br />

schedules differently depending on the reason why it was selected. There<strong>for</strong>e,<br />

make DAILY the second reason to implement different start times or<br />

maximum durations <strong>for</strong> each reason. The next topic explains how to do that<br />

using the schedule's optional reason code record.<br />

For complete in<strong>for</strong>mation on coding criteria statements, see the chapter<br />

"Criteria Language."<br />

To save this criteria record and leave this panel, type FILE in the command<br />

input area. (Otherwise, you could leave the panel without saving this criteria<br />

record by typing QUIT.)<br />

All of the editor commands are inthe appendix "Editor Commands" in the<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> Reference <strong>Guide</strong>, Part 2. The FILE command causes<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> to immediately create that schedule's criteria record.<br />

After you press ENTER, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> displays the following panel,<br />

which confirms that the record has been created:<br />

Chapter 3. Maintaining the Database 3-23

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

Saved successfully!

Ooh no, something went wrong!