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.

6.2 Pitfalls<br />

6.2 Pitfalls<br />

This topic discusses some of the pitfalls you may encounter.<br />

6.2.1 Using Operator Commands on the Status Display Panel<br />

You are able to issue operator commands from a status display by just keying<br />

in the command (first four characters) to the left of the schedule or job. You<br />

can even issue more than one command at a time.<br />

Pitfall:<br />

When keying in a command to the left of a schedule or job in the<br />

Online Status Display, be sure you are on the correct line. It is easy<br />

to cancel the wrong job.<br />

While on the subject of operator commands in status displays, here is a<br />

clarification, not a pitfall. Remember, when using the commands in this<br />

manner, that they are processed sequentially and stop being processed upon<br />

encountering an error. For example, there is no reason to cancel a schedule and<br />

then the jobs in that schedule.<br />

6.2.2 Cancelling and Purging a <strong>Job</strong><br />

Suppose you have a schedule that consists of four jobs: JOB1 through JOB4.<br />

JOB2 requires JOB1; JOB3 requires JOB2; and so on. If you <strong>CA</strong>NCEL JOB3,<br />

whether you also PURGE it, JOB4 will always wait <strong>for</strong> JOB3. You can<br />

manually override this with a POST or FORCE command.<br />

Suppose that JOB3A has JOB3 as a predecessor. If JOB3 is canceled and not<br />

purged, the predecessor JOB3 is ignored when you issue a RUN JOB3A<br />

command because JOB3 has been canceled but is still on the tracking file. If<br />

you purge JOB3 be<strong>for</strong>e issuing the RUN JOB3A command, JOB3A waits <strong>for</strong><br />

JOB3 to complete. You have to RUN JOB3 to put JOB3 back on the tracking<br />

file.<br />

Do not use the PURGE command unless you plan to put the job back on the<br />

tracking file by issuing a RUN command.<br />

Pitfall:<br />

Predecessors <strong>for</strong> jobs added to this day's production using the RUN<br />

command are ignored if they have been canceled by the <strong>CA</strong>NCEL<br />

command but not deleted from the tracking file by the PURGE<br />

command.<br />

6.2.3 Changing Criteria on Selected <strong>Job</strong>s<br />

When a schedule or job has been selected, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> reviews its<br />

predecessor criteria as it exists on the database. What this means is that if you<br />

have a schedule of four jobs: JOB1, JOB2, JOB3, and JOB5, where JOB2 requires<br />

JOB1, JOB3 requires JOB2, and JOB5 requires JOB3. The schedule has been<br />

selected and is on the tracking file. You then add JOB4 and change the<br />

6-20 <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!