Unicenter CA-Scheduler Job Management for VSE User Guide

Unicenter CA-Scheduler uses when ordering the
workload. Schedules and jobs with fewer levels of
predecessors are evaluated ahead of those with
more.
mailbox. The common area for sending Unicenter
CA-Scheduler messages so that they can be viewed
by many users without being deleted.
Manager authority level. The highest authority
level which allows these users to access all stations,
control all schedules and jobs, define and maintain
any database records, and issue all commands. See
General and Supervisor authority levels.
MASTER userid. The userid reserved for the
Unicenter CA-Scheduler administrator.
mask character. An asterisk (*) or question mark (?)
included anywhere in a search string. Used when
you want to display all records with names that
share common characters.
? indicates that any character can be
substituted at this point in the search string,
but just one character can be substituted for
each question mark. That makes ? a
positional mask character.
* indicates that Unicenter CA-Scheduler will
accept anything occurring at this point in the
search: an * can signify any number of
characters. For example:
See generic list.
P? displays all record names of just 2
characters starting with P
P* displays all records that start with the
letter P
?ACC?
displays record names of just five
letters with ACC in the middle
*ACC*
displays just those records with ACC
anywhere in their name
master database. The Unicenter CA-Scheduler
database that stores records containing definitions of
userids, stations, schedules, jobs, and resources. The
default name of the database is CAIJMST.
message record. The record that determines who
receives messages when a schedule or job begins,
ends, or starts late or when a job abends, or is
interrupted. There is a schedule message record
(SMR) and job message record (JMR).
nesting. One procedure calls (retrieves) another
procedure which can, in turn, call another
procedure.
node. Each location in a network having one CPU
or multiple CPUs with multi-access spooling facility.
node record. The record that specifies other nodes
to be notified when a job starts or ends.
null value. A defined value of nothing which has
been added to the database using the keyword
NULL.
on-request. Schedules or jobs having the keyword
REQUESTED in their criteria statement. These
schedules and jobs are selected every day in case
they are needed, but they remain inactive until
activated by the REQUEST or SREQ command.
operator command. A command used to monitor
or control the workload. Also known as control
command.
path. All the stations where a job is processed as it
moves through the data center.
periods. A year can be divided into accounting
periods, production periods, sales cycles, or any
other unit of time. The end of each period is
identified by a P on the datetable.
post-CPU job. Work scheduled after CPU
processing to wrap up a job. Examples include
output decollation, shipment of backup tapes offsite,
and report distribution. See station.
pre-CPU job. Work scheduled to prepare a job for
CPU processing. Examples include daily shipment of
input forms, data entry, and JCL setup. See station.
predecessor. An event that must happen before the
next job can begin. Unicenter CA-Scheduler's
criteria statements allow you to define predecessors
for schedules and jobs which means schedules and
jobs in today's workload will not run until their
predecessors are satisfied. If JOBA is a predecessor
of JOBB, JOBB will not run until JOBA runs to
completion.
Predecessors fall into several different categories that
are defined in this glossary:
Glossary X-5