Network jobs

In the NJE environment, you can pass jobs read into the system through the input service processor to other host nodes in the network for execution service. The input service processor treats jobs you want processed at other nodes in the network the same as jobs you want executed locally. This allows JES2 to determine the node of execution at any time during the scheduling process.

You can route job output from one node to another by:

Specifying a symbolic destination identifier on the following:
- The /*ROUTE PRT JES2 control language statement
- The /*ROUTE PUN JES2 control language statement
- The DD JCL statement,
- The OUTPUT JCL statement.
Using the same symbolic destination identifier as the subscript of the DESTID(jxxxxxxx) initialization statement.

For example, if Node 1 uses a symbolic, PRTBIG, to define a printer on Node 2, NODE 2 can change that printer in the future from remote 7 to remote 8 by specifying R8 on the DEST= parameter without having to advise Node 1 of the change.

At NODE 1, this is the DESTID(jxxxxxxx) initialization statement,

DESTID(PRTBIG) DEST=N2.PRTBIG

At NODE 2, this is the DESTID(jxxxxxxx) initialization statement,

DESTID(PRTBIG) DEST=N2.R7