Unicenter CA-Scheduler Job Management for VSE User Guide

7.5 Multiple CPU Considerations
Normally you would not specify a specific CPU on which a job is to execute.
That is, you would let POWER determine which CPU is available to handle
the job and then let POWER start it on that CPU. This is called centralized
control. If you direct a schedule to a specific CPU by defining the SYSID from
which it will be controlled (by defining the SYSID on the schedule base
record), you will have a degree of decentralized control. The more schedules
you do this to, the more decentralized control you have.
In the case of decentralized control, be aware that the RUN ON SYSID fields
(and the equivalent SYSID batch keywords) on the schedule base record and
job base record perform different functions. RUN ON SYSID on the schedule
base record defines the CPU on which Unicenter CA-Scheduler controls the
schedule (that is, the CPU from which the schedule's jobs are submitted.) On
the other hand, RUN ON SYSID on the job base record specifies the CPU on
which the job actually executes.
The following steps through what happens in the control of a multi-CPU
environment on a daily basis.
Autoscan
During the autoscan process, all schedules that have a SYSID
that matches the one for the CPU on which autoscan is being
run, will be selected for control on that CPU. That is, all jobs
will be submitted from the controlling CPU and internally
Chapter 7. Techniques 7-21