Unicenter CA-Scheduler Job Management for VSE User Guide

7.5 Multiple CPU Considerations
tracked there. Do not forget, the default SYSID is the first one
in your SYSID list specified when generating Unicenter
CA-Scheduler (CAIJGEN macro) and will be used for any
schedule defined without a SYSID.
If the job is actually executed on a CPU other than the
controlling one the other CPU will notify the controlling CPU
of any information it would have picked up itself, such as job
started and job completed, along with the termination code.
This is done by writing information on the tracking file to be
passed along as internal events. If any job is defined without
a SYSID, the default SYSID is the one specified (or defaulted)
at the schedule definition.
Operator Commands
When you issue operator commands, there are times that you
should be aware of which CPU is in control of the schedule or
job. That is, if you issue a CANCEL operator command for a
job that is not controlled on the CPU on which you are on, it
is written to the tracking file and within seconds (could be up
to 30 seconds), processed by the CPU controlling that job. If,
for some reason, the CPU is not able to handle it right away
(suppose it is down), as soon as it can, it will process the
command; even if it is hours later. The area on the tracking
file that passes these operator commands and status
information back and forth between CPUs is called the
Inter-Communication Records area (ICR).
The only operator command that cannot work in a multi-CPU
environment is the STATUS command using the priority
sequence. Since the priority order happens to be an in-core
mechanism, for performance reasons, each CPU has its own
list. Thus, when you request a display of jobs on another
CPU, the priority option cannot be used.
Do keep in mind that any operator commands that are issued
that have to execute on a CPU other than the one they were
issued from, will be sent across the ICR on the tracking file.
They will remain there until actually processed or purged.
When the down CPU becomes operational again and
Unicenter CA-Scheduler is subsequently started, Unicenter
CA-Scheduler determines if it missed an autoscan. If it missed
an autoscan, Unicenter CA-Scheduler immediately performs
an autoscan. If, during this autoscan, Unicenter CA-Scheduler
finds ICRs that are more than 24 hours old, it purges those
old ICRs without executing them.
Another consideration for multiple CPU environments is the
method for executing jobs at a CPU other than the controlling
CPU. To do this on a permanent basis, specify the SYSID of
the CPU at which the job will execute in the RUN ON SYSID
field of the job's base record. To alter the CPU for one
7-22 Unicenter CA-Scheduler User Guide