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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1.1 Beginning with the Basics<br />

1.1 Beginning with the Basics<br />

Ironically, job scheduling <strong>for</strong> multi-million-dollar computers is often handled<br />

with an in-box or a chalk board. With <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>, you can use<br />

the computer you already have to automate production.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> looks at job processing the same way you do: jobs<br />

start and end with the user and a job is not done until the output is delivered.<br />

If you trace the path of a job through your data center, it passes through<br />

different areas be<strong>for</strong>e and after CPU processing:<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> calls each of these areas a workstation and has you<br />

assign numbers to them. Since all sites have JCL setup and CPU processing,<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> assigns those station numbers automatically (stations<br />

39 and 40). Notice that pre-CPU station numbers are in ascending order up to<br />

39. Post-CPU stations are also numbered sequentially and can range from<br />

41-99. This manual will reference the station numbers shown in the diagram<br />

preceding.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> has you number workstations in ascending order <strong>for</strong> a<br />

reason: that sequence tells <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> the logical flow of work<br />

through your data center. Not all jobs are processed at every workstation:<br />

some only run on the CPU, but if a job is scheduled at stations 39 and 40,<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> knows that JCL setup should finish at station 39<br />

be<strong>for</strong>e the job can be submitted to the CPU (station 40). To prevent mistakes<br />

and reruns, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> en<strong>for</strong>ces workstation sequences: all of a<br />

job's pre-CPU work must complete be<strong>for</strong>e its CPU processing can begin.<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> can also think about work the same way you do. If<br />

your production jobs are called AR004 or ARDAILY, use those same names<br />

1-2 <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!