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

■ ■ ■ ■ Explicit predecessors Implicit predecessors Keyword-defined explicit predecessors Selection-defined explicit predecessors predecessor criteria. All of the predecessors defined for a schedule or job in its criteria statement. These predecessor conditions must be satisfied before a schedule can start or a job can be submitted. predecessor loop. The stalemate that occurs when jobs are predecessors to each other. These deadlocked jobs never run because their predecessor conditions are never satisfied. Also called deadlock. procedure. One or more statements cataloged under a procedure name as a member of the CA-Driver procedure library. procedure library. The library that stores Unicenter CA-Driver procedures. production day. The 24-hour period starting with autoscan. Also called the autoscan day. prompt. A word on a screen that reminds you to supply a value. prototype calendar. A master calendar that defines all of the year's holidays and tells when to reschedule jobs that would normally be selected on holidays. These holidays and rescheduling instructions are automatically applied to all calendars defined for that year. prototype definition. An existing definition whose values are used as defaults for a new definition. Any fields left blank while defining a new record are assigned values from the prototype definition. public schedule. A schedule that can be maintained by all users because no value is specified in the USERS field of the schedule base record. queue. One of the various job categories that depend on the status of the jobs. reason. Why a schedule or job is selected for the day's workload. A reason can be: ■ One or more words from the criteria vocabulary or ■ ■ The names of jobs or schedules also selected that day or A combination of the two See selection. reason code. A number that explains why a schedule or job was selected. Numbers from 01 to 79 correspond to the position of a reason in the criteria statement. Numbers from 80 to 99 are special reason codes which indicate that selection was based on default daily processing, calendars, or manual additions. reason code record. The record that assigns time specifications which vary according to the reason a schedule or job is selected for processing. There is a schedule reason code record (SRC) and job reason code record (JRC). RECS line. The line on the bottom of the Schedule Definition (SCHD-SU) panel and Job Definition (SCHD-JU) panel that provides access to panels for optional schedule and job records. reserved-name variable parameter. One of a set of Unicenter CA-Driver variable parameters which are predefined by Computer Associates. resource record. The record which specifies the resources that are used to run a job. route delay time. The delay between the time a job ends at one station and starts at the next station. route station. A workstation defined for purposes of receiving reports rather than performing data processing tasks. run book. A report that contains detailed information on the current day's workload. SBR. Schedule base record. This record is required to define a schedule. schedule. A group of related jobs that: ■ ■ ■ ■ Run on the same days or Belong to the same application or Have the same operational dependencies or Belong together because your production jobs are organized that way X-6 Unicenter CA-Scheduler User Guide

The payroll department's month-end jobs could make up a schedule. The schedules and jobs selected each day comprise the workload. SCR. Schedule criteria record. This record determines when a schedule is to be selected for processing and lists the predecessors for the schedule. selection. How Unicenter CA-Scheduler determines the day's workload at autoscan time. Unicenter CA-Scheduler reviews the criteria statements of every schedule to see which ones qualify for inclusion in the day's workload. Every time Unicenter CA-Scheduler selects a schedule that qualifies, it scans the criteria statements of every job in that schedule. Jobs are selected if: ■ ■ ■ ■ They specify a calendar which defines that day as a workday or A reason in the criteria statement is true that day or No criteria record exists for that job or One reason in the criteria statement is the keyword REQUESTED Jobs can only be selected when the schedules they belong to are selected. All the important terms used in this definition are also defined in this glossary. selection criteria. There are two distinct meanings: 1. All the reasons why a job or schedule can be selected as defined in its criteria statement. If a calendar is also defined for a schedule or job, Unicenter CA-Scheduler bases selection on the calendar and ignores the selection criteria. See selection. 2. The keywords that are used in the maintenance panels to limit the directory to be displayed. selection-defined explicit predecessor. A predecessor that also defines selection criteria. They are schedule or job names used with or without the keywords SCD and START. When START or SCD is used with PRED or DOS, the result is a keyword-defined explicit predecessor that is ignored during the selection process. selection criteria. All the reasons why a job or schedule can be selected as defined in its criteria statement. If a calendar is also defined for a schedule or job, Unicenter CA-Scheduler bases selection on the calendar and ignores the selection criteria. See selection. sequence enforcement. Making sure schedules and jobs are processed in the right order. See implicit predecessor. shared DASD. A hardware configuration that allows two or more operating systems to use the same disk files. This situation allows several operating systems to use the same set of Unicenter CA-Scheduler files at the same time. However, when operating systems share Unicenter CA-Scheduler files, it does not imply that they also share spool files. simulation. Answers the question "what if." It shows how processing is affected by changes in workload or hardware failure. Simulation also totals how long each job usually takes to project when the workload is likely to finish. SIR. Schedule information record. This record provides descriptive information for a schedule. SMR. Schedule message record. This record determines who receives messages when a schedule begins, ends, or starts late. spin locks. The method Unicenter CA-Scheduler uses to protect the integrity of its files when two or more operating systems share them. See shared DASD. SRC. Schedule reason code record. This record is used assign time specifications which vary according to the reason a schedule is selected for processing. staging. Unicenter CA-Scheduler's three-step process for tailoring production JCL: 1. First, Unicenter CA-Scheduler automatically copies the production JCL for jobs that require staging into its staging library. 2. Then users modify that copy of the JCL as needed (the original production JCL is not changed). 3. When the JCL has been modified and that pre-CPU job has been posted as ENDED, Unicenter CA-Scheduler automatically submits the modified JCL to the operating system when that job becomes available for processing. Also called JCL setup. Glossary X-7

The payroll department's month-end jobs could<br />

make up a schedule. The schedules and jobs<br />

selected each day comprise the workload.<br />

SCR. Schedule criteria record. This record<br />

determines when a schedule is to be selected <strong>for</strong><br />

processing and lists the predecessors <strong>for</strong> the schedule.<br />

selection. How <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> determines<br />

the day's workload at autoscan time. <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> reviews the criteria statements of<br />

every schedule to see which ones qualify <strong>for</strong><br />

inclusion in the day's workload. Every time<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> selects a schedule that<br />

qualifies, it scans the criteria statements of every job<br />

in that schedule. <strong>Job</strong>s are selected if:<br />

■<br />

■<br />

■<br />

■<br />

They specify a calendar which defines that day<br />

as a workday or<br />

A reason in the criteria statement is true that<br />

day or<br />

No criteria record exists <strong>for</strong> that job or<br />

One reason in the criteria statement is the<br />

keyword REQUESTED<br />

<strong>Job</strong>s can only be selected when the schedules they<br />

belong to are selected. All the important terms used<br />

in this definition are also defined in this glossary.<br />

selection criteria. There are two distinct meanings:<br />

1. All the reasons why a job or schedule can be<br />

selected as defined in its criteria statement. If a<br />

calendar is also defined <strong>for</strong> a schedule or job,<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> bases selection on the<br />

calendar and ignores the selection criteria. See<br />

selection.<br />

2. The keywords that are used in the maintenance<br />

panels to limit the directory to be displayed.<br />

selection-defined explicit predecessor. A<br />

predecessor that also defines selection criteria. They<br />

are schedule or job names used with or without the<br />

keywords SCD and START. When START or SCD is<br />

used with PRED or DOS, the result is a<br />

keyword-defined explicit predecessor that is ignored<br />

during the selection process.<br />

selection criteria. All the reasons why a job or<br />

schedule can be selected as defined in its criteria<br />

statement. If a calendar is also defined <strong>for</strong> a schedule<br />

or job, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> bases selection on<br />

the calendar and ignores the selection criteria. See<br />

selection.<br />

sequence en<strong>for</strong>cement. Making sure schedules and<br />

jobs are processed in the right order. See implicit<br />

predecessor.<br />

shared DASD. A hardware configuration that<br />

allows two or more operating systems to use the<br />

same disk files. This situation allows several<br />

operating systems to use the same set of <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> files at the same time. However,<br />

when operating systems share <strong>Unicenter</strong><br />

<strong>CA</strong>-<strong>Scheduler</strong> files, it does not imply that they also<br />

share spool files.<br />

simulation. Answers the question "what if." It<br />

shows how processing is affected by changes in<br />

workload or hardware failure. Simulation also totals<br />

how long each job usually takes to project when the<br />

workload is likely to finish.<br />

SIR. Schedule in<strong>for</strong>mation record. This record<br />

provides descriptive in<strong>for</strong>mation <strong>for</strong> a schedule.<br />

SMR. Schedule message record. This record<br />

determines who receives messages when a schedule<br />

begins, ends, or starts late.<br />

spin locks. The method <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />

uses to protect the integrity of its files when two or<br />

more operating systems share them. See shared<br />

DASD.<br />

SRC. Schedule reason code record. This record is<br />

used assign time specifications which vary according<br />

to the reason a schedule is selected <strong>for</strong> processing.<br />

staging. <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong>'s three-step<br />

process <strong>for</strong> tailoring production JCL:<br />

1. First, <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> automatically<br />

copies the production JCL <strong>for</strong> jobs that require<br />

staging into its staging library.<br />

2. Then users modify that copy of the JCL as<br />

needed (the original production JCL is not<br />

changed).<br />

3. When the JCL has been modified and that<br />

pre-CPU job has been posted as ENDED,<br />

<strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> automatically submits<br />

the modified JCL to the operating system when<br />

that job becomes available <strong>for</strong> processing.<br />

Also called JCL setup.<br />

Glossary X-7

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

Saved successfully!

Ooh no, something went wrong!