Unicenter CA-Scheduler Job Management for VSE User Guide

7.7 Summing Up
7.7 Summing Up
The following is a review of the important principles outlined previously.
7.7.1 On-Request Schedules and Jobs
Remember these subtleties when defining a criteria statement containing the
keyword REQUESTED:
■
■
A criteria statement of REQUESTED causes Unicenter CA-Scheduler to put
that schedule or job and its successors in the inactive queue at autoscan.
When OR REQUESTED occurs in a criteria statement, Unicenter
CA-Scheduler will select that schedule or job daily. However, whether it is
put in the inactive queue depends on the reason for selection. If selection
occurs because of REQUESTED, that schedule or job is placed in the
inactive queue. Therefore, the order of reasons in a criteria statement really
matters a lot if one of the reasons is requested.
When a schedule or job is selected because of REQUESTED, all its successors
are put in the inactive queue. Issuing a REQUEST command moves a schedule
or job and all its successors to the active queue. The SREQ command handles
successors differently: SREQ will not activate a successor if it involves other
requested jobs. A successor of an SREQed schedule or job will not be moved
to the active queue if:
■
■
The successor's criteria statement contains the keyword REQUESTED or
That successor is also the successor of some other requested job in the
inactive queue
7.7.2 Backlogged Work
If work is backlogged for more than 48 hours, it is likely that the second day's
schedule will never run. Monitor your backlogged work carefully.
7.7.3 Online Commands in Batch
The CAJUCMD0 program can process six types of batch transactions:
Prefix
CP
MO
SC
CI
Transaction Type
Issue the following VM command.
Send the following text to the operator console.
Issue the following Unicenter CA-Scheduler operator
command, which can include the conditional batch IF
statement.
CICS Transactions
7-34 Unicenter CA-Scheduler User Guide