Unicenter CA-Scheduler Job Management for VSE User Guide

7.6 NJE Processing
7.6 NJE Processing
NJE processing provides the ability to go beyond one data center complex.
That is, you can schedule and control production at different locations (even in
different cities). The different locations can have just one CPU or they may
have a multi-CPU environment, though each CPU must be a node on the
VTAM network.
In some cases, you may want to have just interdependencies across locations
properly handled. In other cases, you may want to go beyond this and have
jobs at one location submitted to execute at another location. These locations
are called nodes in the network of computer sites (or systems). The network
consists of two or more of these interconnected systems (nodes) that
participate in a VTAM communications network.
Using more common terminology, a job at one node can have a predecessor at
another node and Unicenter CA-Scheduler will know to wait for it. Each node
will be able to schedule its own work as if it were autonomous, but when it
has interrelationships with other nodes, they will be upheld properly. This is a
decentralized (Master/Master) environment. Each of these Master
environments (nodes) can have its own Master/Master or Master/Slave
environment and may be one or more CPUs themselves that utilize shared
spool.
Following are some samples that describe:
■
■
■
Cross-node job submission
Cross-node dependencies
Cross-node communications.
7.6.1 Cross-Node Job Submission
In a NJE environment, it is possible to have Unicenter CA-Scheduler cause
work to be submitted to run on other nodes. The appropriate VSE/POWER
JECL parameters (if omitted from the submitted JCL) are generated to handle
this, but what you want to accomplish here is to have you understand how
Unicenter CA-Sheduler operates in this environment.
The following depicts the general environment that the samples will reference.
7-26 Unicenter CA-Scheduler User Guide