Unicenter CA-Scheduler Job Management for VSE User Guide

7.5 Multiple CPU Considerations
If you knew the outage was going to be short, you could
MOVEOVER specific schedules by issuing this command for
each schedule you want moved over. The TARGET field is
optional and defaults to the CPU on which the MOVEOVER
command is being issued. It gives you the flexibility to issue
the command and cause it to be executed on another CPU.
At some point, the original Master CPU is available. It must
be given back control of Unicenter CA-Scheduler. Thus, you
use the operator command (from SYSID 1):
SC MOVEOVER RESTORE=Y
which will cause all schedules (even those currently executing)
that were controlled originally by the CPU that was down, to
be moved back.
Centralized
In a centralized environment, there are no schedules that have
a user-specified SYSID from which they are controlled. This
means that you have never filled in the RUN ON SYSID field
when using the Schedule Definition panel. Consequently, all
jobs will be controlled on the first SYSID in the list of SYSIDs
defined in the CAIJGEN macro which is the the Master CPU.
All other CPUs in the list are Slave CPUs.
The simplest case is that if a Slave CPU is down, nothing has
to be done with Unicenter CA-Scheduler as POWER will have
been changed in a manner to handle this situation.
Now consider what must be done if the Master CPU goes
down. One of the Slave CPUs must be made the Master so
that Unicenter CA-Scheduler can continue controlling the
schedules and jobs. The workload from the Master CPU must
be moved over to the Slave CPU and the Slave CPU made to
simulate the Master CPU. You may do this by executing a
batch program, CAJMMOV0, but first you must use the
SHUTDOWN operator command to shutdown Unicenter
CA-Scheduler, then run the following job on the slave CPU.
// JOB CAJMMOV
// EXEC CAJMMOV
/
/&
After the job completes, bring up Unicenter CA-Scheduler on
that CPU again. It will now perform as the Master CPU.
Executing the CAJMMOV0 program on a CPU has a "permanent" effect, in that
the CPU will become the Master (control all schedules and jobs, and perform
AUTOSCAN) until the program is executed on a different CPU. If for any
reason a format of the tracking file becomes necessary, you must run
7-24 Unicenter CA-Scheduler User Guide