Unicenter CA-Scheduler Job Management for VSE User Guide

5.1 Criteria Vocabulary
Two types of explicit predecessors have been described so far:
keyword-defined and selection-defined.
Implicit predecessors are predecessors that do not have to be defined in the
criteria. When the same schedule/job/job-number exists for more than one
station (01 - 99), the sequential order of the stations defines implicit
predecessors. For example, a CPU job on station 40 will always have an
implicit predecessor of its staging job on station 39, if both are in the day's
workload. Further, implicit predecessors are automatically selected on the
same day that the CPU job (station 40) is selected. You can, however, code
criteria for them to be selected less frequently than the CPU job. Note,
however, that you cannot cause implicit predecessors to be selected on a day
the CPU job is not selected.
Furthermore, implicit predecessors can only exist for CPU jobs and post-CPU
jobs. For example, a CPU job will not be submitted until all its pre-CPU jobs
complete. Likewise, post-CPU jobs will not be started until their CPU jobs have
ended.
5.1.5 Using Multiple Conditions with ANDs and ORs
The examples that have been used so far have contained only one reason. That
is, the condition or combination of conditions, individually caused the reason a
job or schedule was selected.
The way you separate reasons is with an OR outside of a set of parentheses or
with an OR if no parentheses are being used. For example,
MON AND JOB1 OR TUE AND JOB2
is the same as
(MON AND JOB1) OR (TUE AND JOB2)
Use parentheses as a normal convention since it more clearly depicts your
intention. All of our examples will appear with parentheses.
The reason a job is selected stays with the job for its life in the system. In the
example preceding, the value 01 would be the reason if it was selected because
it was (MON AND JOB1). The value 02 would be the reason if it was (TUE
AND JOB2). This value can be referred to as the reason code.
Understanding the relationships between reasons and predecessors is
important. Since the criteria language is used to define both selection and
predecessor conditions, there are rules for interpreting this mixture.
Rule #1
Every Unicenter CA-Scheduler-controlled job or schedule listed in a
criteria statement is a predecessor if it is also in the day's
production. Whether those jobs or schedules are part of the reason
for selection does not matter.
Chapter 5. Criteria Language 5-7