z/OS JES2 Initialization and Tuning Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Network connection control records

z/OS JES2 Initialization and Tuning Guide
SA32-0991-00

The path manager sends network connection control (NCC) records between JES2 nodes to establish NJE connections and keep track of non-adjacent connections. The path manager uses the NCC records to update the path manager routing tables that establish the path manager's view of the network. These network updates occur through the M and N records that add and subtract members from a network, respectively.

The path manager determines the best path based upon the path of least resistance between the local node and each other node in the network. The resistance is derived from NCC records, CONNECT initialization statements, and parameters on the NJEDEF, NODE(nnnn), APPL(avvvvvvv), and LINE(nnnn) initialization statements. For more information on how the path manager uses these specifications for both adjacent and non-adjacent connections, see Determining path resistance.

The following is a list of the network connection control records. Only JES2 uses those records denoted by an asterisk (*).
Record
Purpose
I
Initial Signon
J
Response Signon
K
Reset Signon*
L
Concurrence Signon *
M
Add Connection *
N
Subtract Connection *
B
Signoff
Note that the path manager does not send records about the following connections:
  • Predefined or static connections (using a CONNECT initialization statement)
  • Non-path manager connections
  • Private connections

Non-JES2 nodes (such as JES3, RSCS, and System i®) discard NCC M and N records.

See Displaying information about a network for an example of how to display all active paths to a node.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014