If JES2 does not make a number of connections, you can enter a $D NODE(*) command to list all the nodes and a $D CONNECT command to list their connections. Make sure you route the output of this command to the hard-copy log as it can be quite large and difficult to read on the console. Also, entering a $D PATH(nodename) command shows you the paths to one or more nodes as defined to JES2. See z/OS JES2 Commands for more information about the $D PATH(nodename) command. If the connection was delayed or not completed, message $HASP501 is issued, listing the member that did not respond.

If the node involved is a non-JES2 node, you need to ensure that the initialization statements that define the connection are correct. z/OS MVS Initialization and Tuning Guide discusses the considerations for connecting non-JES2 nodes.

Examine SYSLOG to see if JES2 issued any resource shortage messages. A shortage of teleprocessing (TP) buffers or lines can cause connection failures. Also, message $HASP676 indicates network-specific resource shortages. JES2 issues messages $HASP676 and $HASP679 on the system initiating the connection to indicate the cause of the connection failure. The node on the receiving end of the connection may receive message $HASP223, which indicates network-specific resource shortages on that node. In either case, the node with the shortage may require a warm start before the connection can complete.

You can increase the number of teleprocessing buffers available by using the $T TPDEF command. See z/OS MVS Initialization and Tuning Guide for more information about teleprocessing buffers.