Unicenter CA-Scheduler Job Management for VSE User Guide

5.1 Criteria Vocabulary
Rule #2
A job will only be evaluated for selection and eligible for today's
workload if its schedule is selected or eligible for today's workload.
For example, if the selection criteria for SCHED1 is MON, and JOB1A in
SCHED1 has a selection criteria of TUES, JOB1A will never get selected. JOB1A
is only looked at if its schedule is selected but SCHED1 is not selected on
Tuesdays, so JOB1A will never be selected.
Rule #3
When coding a job in the criteria language, always qualify it with
its schedule name.
Previously we have not followed the preceding rule for simplicity's sake
because schedule names technically are not required. However, if you omit a
schedule name when referring to a job, Unicenter CA-Scheduler looks in its
database and defaults to the first schedule it finds containing a job by that
name.
To specify a unique job, use this format:
jobname[-jobnumber] [station] [schedule]
Any or all of the three optional parameters (job number, station, and schedule)
may be omitted, but the order in which they are specified is significant. Notice
that the job number must be connected to the job name with a hyphen (-) and
no intervening blanks. For example, this is how to specify JOBA in SCHDA
with a job number of 02 at station 39:
JOBA-2 39 SCHDA
This format can be used with any of the reserved words that are valid for
defining predecessor jobs (PRED, VSE, or START).
If you run simulation, be careful how you use the REQUESTED keyword. To
ensure that simulation reports return reason codes that match those produced
by Unicenter CA-Scheduler on the online status displays (SCHEDULER
Command Processor panel), specify REQUESTED after job and schedule names
in selection criteria whenever possible.
A schedule is eligible for selection even if AUTO SELECT=NO is specified.
Chapter 5. Criteria Language 5-9