Unicenter CA-Scheduler Job Management for VSE User Guide

7.6 NJE Processing
Sample 5
Sample 6
In summary
Schedule SCHDY is defined at NODEB with a NODE ID of
NODEA and RUN ON SYSID of 2. JOB1 is defined as part of
schedule SCHDY and does not have a NODE ID specified, but
does have RUN ON SYSID of 3.
In this case, NODEB controls the schedule SCHDY at the CPU
with SYSID 2. JOB1 within SCHDY will be routed to NODEA
to run since its NODE ID is not defined and it picks up the
one from its schedule which is NODEA. Since there is no
NODE SYSID on the job or its schedule, it will run according
to the definitions at NODEA that, in this sample, would be 1.
The RUN ON SYSID of 3 at the job level, in this case, will be
ignored.
Schedule SCHDY is defined at node NODEB with no NODE
ID or NODE SYSID. JOB1 is defined as part of schedule
SCHDY and has a NODE ID of NODEA and a RUN ON
SYSID of 3.
In this case, NODEB controls the schedule SCHDY at the CPU
that is defined as the controlling CPU with the Unicenter
CA-Scheduler SYSGEN definitions (described in the prior
topic on Multiple CPU Considerations). JOB1 within SCHDY
will be routed to NODEA to run since its NODE ID of
NODEA overrides anything defined at the schedule level.
Since there is no NODE SYSID on the job or its schedule, it
will run according to the definitions at NODEA that, in this
sample, would be 1. The RUN ON SYSID of 3 at the job level
will, again, be ignored.
This gives you some insight into how jobs can be defined on
one node and submitted to run on another node.
7.6.2 Cross-Node Dependencies
The only predecessor events that can be fed back and forth between nodes are
NJE start or completion of job events.
In the case of job predecessors across nodes, you must define a job node record
if Unicenter CA-Scheduler is to inform another node or nodes (up to eight)
that this job started or completed. You do this with the INFORM Definition
panel.
The following discusses each of these types of predecessors and how to define
them.
7-28 Unicenter CA-Scheduler User Guide