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.

1.2 How <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> Works<br />

■<br />

■<br />

Display the current values of <strong>Unicenter</strong> <strong>CA</strong>-Driver reserved variable<br />

parameters<br />

Change the values of any <strong>Unicenter</strong> <strong>CA</strong>-Driver reserved variable<br />

parameters be<strong>for</strong>e each job's staging at workstation 39 is posted as<br />

complete.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> assists in managing production job rerun/restart in<br />

many different ways:<br />

■<br />

■<br />

■<br />

■<br />

A backout job can be automatically submitted to undo the effect of an<br />

abended job.<br />

A schedule can be automatically added to the workload when a job<br />

abends. The schedule can include any number of jobs to recover from or<br />

restart the abended job.<br />

The <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> utility program can be embedded in the<br />

production JCL after strategic job steps, and can trigger different recovery<br />

schedules depending on the abended step.<br />

<strong>Unicenter</strong> <strong>CA</strong>-Driver procedures can be developed to automatically<br />

generate different job streams depending on the abending step when a job<br />

is submitted <strong>for</strong> a rerun.<br />

False job completion frequently occurs. It is a case in which a job appears to<br />

have run successfully (that is, no abend conditions or fail code returned from<br />

the job), but in reality the job did NOT run successfully. The evidence is on the<br />

job output (job log), or in the contents of the report produced by the job, or in<br />

a message issued to the operator console by the job. False job completion<br />

could be very costly when passed undetected since <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />

could submit numerous successors to a job that appeared to have run<br />

successfully. Through the Auto-Reply processing facility false job completion<br />

can be automatically detected and prevented. This is done by checking<br />

console output <strong>for</strong> a job be<strong>for</strong>e <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> posts the job as<br />

complete.<br />

<strong>User</strong>s can communicate with <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> in online or batch mode.<br />

All of the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> monitoring functions are available from the<br />

operator console as well. Online access is supported <strong>for</strong> CICS, CMS and ICCF.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> users can be assigned three levels of authority to<br />

control what they can and cannot do. Controlling schedules can be limited to<br />

authorized users. <strong>User</strong>s can also be limited to controlling jobs at certain<br />

stations.<br />

Security exits are also available <strong>for</strong> enhanced protection.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> automatically updates the status of all CPU jobs in the<br />

tracking file. <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> assigns status conditions to jobs to<br />

indicate the state of their progress within production. Only authorized users<br />

can issue the commands that alter the status of tasks per<strong>for</strong>med at other<br />

stations.<br />

Chapter 1. Introduction 1-9

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

Saved successfully!

Ooh no, something went wrong!