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.

3.9 Defining <strong>Job</strong>s<br />

However, sometimes production JCL requires editing be<strong>for</strong>e it can be<br />

submitted. STAGE JCL fields on the schedule and job base records identify<br />

which jobs have JCL that requires editing be<strong>for</strong>e submission. Again, the value<br />

of STAGE JCL on the job record overrides the one defined <strong>for</strong> the schedule. If<br />

STAGE JCL = YES, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> copies that job's production JCL<br />

into the staging library when the job is selected. You can then define an<br />

EARLIEST START TIME that allows plenty of time to edit the staged JCL<br />

be<strong>for</strong>e this job is submitted. Or you can ensure that the JCL has been edited<br />

be<strong>for</strong>e submission by defining another record <strong>for</strong> this job at station 39 (JCL<br />

setup). Defining a job record <strong>for</strong> station 39 guarantees that <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> will not submit this job <strong>for</strong> processing until that JCL has been<br />

edited and staging is complete.<br />

In the case where the JCL <strong>for</strong> a specific job is stored in a <strong>CA</strong>-Panvalet library,<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> will submit a batch job that is a library access job.<br />

This job will run in a partition and extract the actual job JCL from the library<br />

and submit this JCL to POWER to be run so that this JCL may not be staged.<br />

Once the JCL is staged, you can use a variety of editor commands to prepare it<br />

<strong>for</strong> submission. In addition to usual text editing, you can per<strong>for</strong>m some<br />

special functions within the editor:<br />

■<br />

■<br />

■<br />

Expansion of <strong>Unicenter</strong> <strong>CA</strong>-Driver procedures embedded in the JCL<br />

Display of current values of all <strong>Unicenter</strong> <strong>CA</strong>-Driver reserved-name<br />

variable parameters in the JCL<br />

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

parameters in the JCL<br />

For detailed explanations of the editor commands, see the appendix "Editor<br />

Commands" of the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> Reference <strong>Guide</strong> Part 2.<br />

3.9.3.6 On Which CPU Should <strong>Job</strong>s Be Run?<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> uses three fields on both schedule and job base<br />

records to record where jobs run:<br />

■<br />

■<br />

■<br />

NODE ID<br />

NODE SYSID<br />

RUN ON SYSID<br />

Whether you need to define these fields depends on the CPU configuration at<br />

your site:<br />

If You<br />

Only have one CPU<br />

Do This<br />

Leave all three fields blank on both schedule and<br />

job records.<br />

3-66 <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!