Controlling JES3 networking

JES3 networking permits your JES3 complex – the home node – to be part of a job entry network that can include one or more additional systems or complexes – the remote nodes. Using JES3 networking, you can transmit jobs, job output (SYSOUT), commands, and messages to any node in the network for processing.

JES3 provides three networking protocols: binary synchronous communication/network job entry (BSC/NJE), systems network architecture/network job entry (SNA/NJE), and TCP/IP/network job entry (TCP/IP/NJE). This topic presents information about SNA/NJE, BSC/NJE, and TCP/IP/NJE in the following sequence:

Controlling BSC/NJE
Controlling SNA/NJE
Controlling TCP/IP/NJE

SNA/NJE, BSC/NJE and TCP/IP/NJE can coexist in the same JES3 complex. You must, however, use the protocol that matches the one being used by the one or more nodes that are directly connected to your node to establish a networking session.

All the characteristics of a network, as seen from your perspective of installation (the home node), are defined during JES3 initialization. These characteristics include:

The nodes in the network
The path used to transmit data to each node in the network
The consoles used to receive networking messages
The protocol in use for each node (SNA/NJE, BSC/NJE, or TCP/IP/NJE)
A routing table for inbound commands from the network
The communication lines connecting your node with adjacent nodes (BSC/NJE only)

After JES3 completes initialization and before you can send or receive messages or commands from other nodes in the network, you must start networking console support.

To start BSC/NJE, you must start communication lines or channel-to-channel adapters (CTCs) that connect your node with adjacent nodes.

To start processing inbound SNA/NJE network jobs at the home node, you must start at least one NJE reader (NJERDR DSP).

To start TCP/IP/NJE, you must call the TCP DSP for a Netserv (this action starts the Netserv address space) and start at least one socket to the node that you want to communicate with. If the remote node is either JES2 or JES3, you must start a Netserv (NETSRV on JES2) on that node as well. You need to only start a socket in one direction; however, if the remote node is JES2, there must be a socket definition from the JES2 node to your home node, even if you are starting the socket from your node.

Once communication is established, you can use commands to control activity in the network. For all changes that affect other nodes, be sure to ask your system programmer for help in coordinating the changes with the operations staff at the other nodes. In some cases, you must coordinate the content and timing of the changes to avoid losing data that is being transmitted or to avoid system problems in one or more nodes in the network.

The results of all modifications described in this topic are lost if the node being modified is SNA or BSC and you restart JES3. Modifications to TCP/IP nodes are retained if you restart JES3.

The JES3 networking commands contain several keywords. You can enter the keywords as they appear or you can abbreviate the keywords as follows:

LINE or L
PATH or P
JOB or J
NAME or N
JOBGROUP or JG
ADD or A
DEL or D

Some JES3 commands can be entered from other nodes within the network. For more information about the commands you can enter through NJE, see Using JES3 to authorize commands from NJE.

The network your installation belongs to is composed of three nodes. Your installation, the home node, is node A. Figure 1 illustrates the configuration of your network.

Figure 1. The Original Network

If you want to add node D to the network at node A, you must issue the following command:

*F,NJE,ADD=D

Figure 2 illustrates the new configuration of your network.

Figure 2. The Network with Node D Added

JES3 adds the specified node to your network as an indirectly-connected node.

IAT8460 NJERMT UPDATE COMPLETE. REQUEST HONORED.

The network your installation belongs to is composed of three nodes. Your installation, the home node, is node A. Figure 3 illustrates the configuration of your network.

Figure 3. The Original Network

If you want to add node D to the network at node C, you must issue the following command at node A:

*F,NJE,ADD=D,PATH=B

If you do not indicate the path with the PATH= parameter, JES3 will add the node as a directly-connected node. Figure 4 illustrates the new configuration of your network.

Figure 4. The Network with Node D Added

Note: The NAME and PATH operands are not positional; you can enter them as they appear or you can use N= and P= respectively. See z/OS JES3 Initialization and Tuning Guide for more information about establishing a network.

JES3 deletes the specified node from your network.
If you delete an active SNA node, work for that destination is placed in operator hold. JES3 will issue messages to indicate the node is no longer included in the network.
You cannot delete an active TCP/IP node, or any TCP/IP node that has sockets defined, regardless of whether the node is active.
You cannot delete a TCP/IP node that has sockets defined, regardless of whether the node is active.

IAT8460 NJERMT UPDATE COMPLETE. REQUEST HONORED.

The network your installation belongs to is composed of four nodes. Your installation, the home node, is node A. Figure 5 illustrates the configuration of your network.

Figure 5. The Original Network

If you want to delete node D from the network, you must issue the following command:

*F,NJE,DEL=D

Figure 6 illustrates the new configuration of your network.

Figure 6. The Network with Node D Deleted