Unicenter CA-Scheduler Job Management for VSE User Guide
Share Embed Flag
Download ePaper

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

supportcontent.ca.com
from supportcontent.ca.com More from this publisher
03.03.2015 Views

3.1 Defining Schedules 3.1.4.3 What JCL Does Unicenter CA-Scheduler Submit for These Jobs? JCL for jobs under Unicenter CA-Scheduler control can be manually submitted to the reader queue, but Unicenter CA-Scheduler can even automate that step for you. Unicenter CA-Scheduler can retrieve JCL directly from ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ AllFusion CA-Panvalet, AllFusion CA-Librarian User-defined libraries A Unicenter CA-Driver procedure library A CMS member An ICCF member An SLI source member A PROC VSE procedure library Allfusion CA-Vollie library member CONDOR However, sometimes production JCL requires editing before it can be submitted. Two schedule fields tell Unicenter CA-Scheduler where to find the JCL to submit for jobs in that schedule: STAGE JCL and LIBRARY TYPE. Unicenter CA-Scheduler first determines which library contains the JCL for these jobs by checking the LIBRARY TYPE. Then Unicenter CA-Scheduler checks to see if this JCL requires editing. Since you can override a schedule's value for STAGE JCL at the job level, Unicenter CA-Scheduler checks both schedule and job base records. If STAGE JCL = NO, Unicenter CA-Scheduler knows it can submit the production JCL directly to the CPU. However, if STAGE JCL = YES, Unicenter CA-Scheduler copies the production JCL into the staging library as soon as the job is selected. After that JCL has been edited and staging is complete, Unicenter CA-Scheduler submits the edited JCL for processing. In the case where the JCL for a specific job is stored in a CA-Panvalet or OWL library, Unicenter CA-Scheduler will submit a batch job that is a library access job. This job will run in a partition and extract the actual job JCL from the library and submit this JCL to POWER to be run. 3.1.4.4 Which CPU Should Control These Jobs? The RUN ON SYSID field is used only in a multi-CPU environment. When specified within a schedule definition, the RUN ON SYSID field value designates a POWER SYSID that is then associated with the CPU that will control and submit the jobs within that schedule. Do not specify a RUN ON SYSID within a schedule definition if you have a Unicenter CA-Scheduler Master/Slave, multi-CPU environment. This environment determines the controlling CPU from the CAIJGEN installation macro. 3-14 Unicenter CA-Scheduler User Guide

3.1 Defining Schedules If your site has one CPU perform scheduling for all of them, it is called your Master CPU. It is the first CPU listed on the SYSID= installation generation macro parameter. Since that value is the default for a schedule's RUN ON SYSID, you must leave that field blank on the schedule base record if your site has a Master CPU. NODE ID and NODE SYSID are only used at sites that are part of a network that uses POWER/VSE at each node and Unicenter CA-Scheduler on each CPU at every node. Only use NODE SYSIDs if there are multiple CPUs using shared POWER spool at a NODE ID. Also notice that values for these fields mean different things on schedule and job records. NODE ID on the schedule record indicates the default NODE ID for the jobs in that schedule. A job's NODE ID identifies which node the job's JCL is submitted to. If a job runs on the node specified as the schedule's NODE ID, you can leave NODE ID blank on the job record. To submit a job to another node, specify its node ID on the job base record. Suppose there are multiple CPUs at this node. Use NODE SYSID to specify a particular CPU if the node has multiple CPUs that each run Unicenter CA-Scheduler and share a POWER location. For NODE SYSID, enter the POWER SYSID of the remote CPU where the job is to run. NODE SYSID is only valid if NODE ID is also specified on the same record. When NODE ID and NODE SYSID are given, that job base record's value for RUN ON SYSID is ignored. 3.1.4.5 What Schedule Fields Are Used for Simulation? Simulation is one of Unicenter CA-Scheduler's most powerful features. Without actually running your workload, Unicenter CA-Scheduler can produce reports showing ■ ■ ■ ■ ■ ■ Which jobs would be selected What resources would be required When and where each job would be processed How heavily each device would be utilized Which jobs would be late Which jobs would carry over to the next day Such a planning tool gives Unicenter CA-Scheduler users an advantage when dealing with the situations that confront a data center daily. Therefore, it is worth your while to supply the values needed for simulation. AVERAGE TIME allows you to specify the average processing time in days, hours, and minutes. Leading zeros can be omitted. This optional field is only used to prepare simulation reports. Use this field to have simulation reports project the overall effect of a change in average processing time for this schedule. If a time is not specified here, simulation uses the schedule's actual average processing time based on historical $JOBACCT data. Chapter 3. Maintaining the Database 3-15

3.1 Defining Schedules<br />

If your site has one CPU per<strong>for</strong>m scheduling <strong>for</strong> all of them, it is called your<br />

Master CPU. It is the first CPU listed on the SYSID= installation generation<br />

macro parameter. Since that value is the default <strong>for</strong> a schedule's RUN ON<br />

SYSID, you must leave that field blank on the schedule base record if your site<br />

has a Master CPU.<br />

NODE ID and NODE SYSID are only used at sites that are part of a network<br />

that uses POWER/<strong>VSE</strong> at each node and <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> on each<br />

CPU at every node. Only use NODE SYSIDs if there are multiple CPUs using<br />

shared POWER spool at a NODE ID. Also notice that values <strong>for</strong> these fields<br />

mean different things on schedule and job records.<br />

NODE ID on the schedule record indicates the default NODE ID <strong>for</strong> the jobs in<br />

that schedule. A job's NODE ID identifies which node the job's JCL is<br />

submitted to. If a job runs on the node specified as the schedule's NODE ID,<br />

you can leave NODE ID blank on the job record. To submit a job to another<br />

node, specify its node ID on the job base record.<br />

Suppose there are multiple CPUs at this node. Use NODE SYSID to specify a<br />

particular CPU if the node has multiple CPUs that each run <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> and share a POWER location. For NODE SYSID, enter the<br />

POWER SYSID of the remote CPU where the job is to run. NODE SYSID is<br />

only valid if NODE ID is also specified on the same record. When NODE ID<br />

and NODE SYSID are given, that job base record's value <strong>for</strong> RUN ON SYSID is<br />

ignored.<br />

3.1.4.5 What Schedule Fields Are Used <strong>for</strong> Simulation?<br />

Simulation is one of <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>'s most powerful features. Without<br />

actually running your workload, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> can produce reports<br />

showing<br />

■<br />

■<br />

■<br />

■<br />

■<br />

■<br />

Which jobs would be selected<br />

What resources would be required<br />

When and where each job would be processed<br />

How heavily each device would be utilized<br />

Which jobs would be late<br />

Which jobs would carry over to the next day<br />

Such a planning tool gives <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> users an advantage when<br />

dealing with the situations that confront a data center daily. There<strong>for</strong>e, it is<br />

worth your while to supply the values needed <strong>for</strong> simulation.<br />

AVERAGE TIME allows you to specify the average processing time in days,<br />

hours, and minutes. Leading zeros can be omitted. This optional field is only<br />

used to prepare simulation reports. Use this field to have simulation reports<br />

project the overall effect of a change in average processing time <strong>for</strong> this<br />

schedule. If a time is not specified here, simulation uses the schedule's actual<br />

average processing time based on historical $JOBACCT data.<br />

Chapter 3. Maintaining the Database 3-15

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!