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.1 Commonly Asked Questions<br />

6.1.4.3 Summary<br />

For jobs in the tracking file:<br />

■<br />

■<br />

■<br />

Use RERUN or SUBMIT <strong>for</strong> jobs that ended abnormally or were canceled.<br />

Use FORCE to submit jobs if you are willing to violate their reasons <strong>for</strong><br />

waiting.<br />

Use requested or SREQ <strong>for</strong> requested jobs.<br />

For jobs not on the tracking file:<br />

■<br />

■<br />

Use ADD to put a job on the tracking file if it does not exist on the<br />

database or if it is on the database, but you need to change its keywords.<br />

Use RUN to submit jobs in the database if you do not need to change their<br />

keywords.<br />

6.1.4.4 When Is the PRED Flag Reset?<br />

When you use the PRED keyword in the criteria language, it indicates that the<br />

schedule or job is to wait <strong>for</strong> a predecessor to complete. When you do not use<br />

the keyword PRED, the predecessor is to complete within the autoscan day.<br />

When you specify PRED in front of the predecessor, it means the predecessor<br />

was to have completed since the last time this schedule or job was run. There<br />

is an exception, however. If the PRED is a schedule or job that is in today's<br />

workload, it will wait <strong>for</strong> that specific one to complete. For example, if a job<br />

has a predecessor of PRED DSN JOBA.MASTER, the output data set<br />

JOBA.MASTER must have been closed at least once between each running of<br />

that job. If the job is run weekly, then it must have been closed at least once<br />

during the last week.<br />

Normally in the selection process (during autoscan), job names cause selection<br />

if the predecessor job was selected. When PRED precedes a schedule name or<br />

job name, it is not used in determining selection, but is a predecessor condition<br />

only. All other criteria rules still apply.<br />

6.1.4.5 What Happens If There Was a System Crash?<br />

The following discussion is appropriate to a system crash or if <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> does not complete normally.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> is able to recognize whether a clean shutdown<br />

occurred. When a clean shutdown did not occur, upon starting back up,<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> does the following based on the status of the job at<br />

the point <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> was last active:<br />

Status At Failure<br />

STARTED<br />

Sets New Status To<br />

UNKNOWN - The job may have to be rerun, but<br />

requires investigation by a troubleshooter.<br />

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