Unicenter CA-Scheduler Job Management for VSE User Guide

7.6 NJE Processing
7.6.2.1 NJE Job Dependencies
When a predecessor of a schedule or job is a job controlled by another node,
then you use the NJE keyword. The NJE keyword only pertains to jobs, not
schedules. NJE can take any one of the following forms:
NJE Form
NJE jobname
START NJE jobname
PRED NJE jobname
Predecessor Type Is
The completion of a job at another node.
The start of a job at another node.
The completion of a job at another node on a
previous day.
To mark an NJE predecessor job as satisfied, its definition must include
instructions for Unicenter CA-Scheduler to notify the relevant node or nodes.
You do this using the INFORM Record Definition panel. That is, if a job
controlled from NODEA has NJE JOBA as a predecessor and you never
defined a job INFORM Definition panel for JOBA and JOBA runs at a node
other than NODEA, then NODEA will never be notified that JOBA completed.
Consequently, the job on NODEA will never be submitted.
Remember two things when dealing with predecessor jobs across nodes. First,
use the NJE keyword, and second, use the INFORM Definition panel. Thus,
you close the loop.
7.6.3 Cross-Node Command Processing
Control commands can be issued on one node and processed on another node.
You do this by using the RO (ROute=nodeid) keyword in the corresponding
control command. The node to which you are directing the command must be
active. Practically all of the commands offer this keyword. An example of
cross-node communications follows.
The environment used in the preceding example consists of three nodes
running NJE using the Unicenter CA-Scheduler NJE option. Each node
consists of a single CPU.
Chapter 7. Techniques 7-29