A connection involves 2 points in a network. Each point is the smallest addressable piece of the network and a single JES2 member. A CONNECT statement specifies 2 points that are to be connected. Each point is identified by its node with a member number of 1.

Use the MEMBerA= and MEMBerB= parameters to see various members of the shared spool (on the nodes defined by the NodeA= and NodeB= parameters) involved in the connection. The MEMBerB= parameter has the same meaning for NodeB as the MEMBerA= has for NodeA. You should always specify a value of 1, unless you know that the node to which you are connecting has specified a different value.

Figure 1 shows that nodes 1 and 2 have a static connection because of the CONNECT statements in their initialization data sets.

    CONNECT NODEA=BOST1,MEMBERA=1,NODEB=NYC2,MEMBERB=1,REST=150

The NodeA= and NodeB= designations provide a means of specifying the two nodes that make up the connection (node 1 and node 2 in the example).

Figure 1. Static Connections

The REST= parameter specifies the total resistance of the connection between BOST1 (node 1) and NYC2 (node 2).

Static connections are not propagated to other nodes, and are therefore private. A private connection is known only to those systems comprising the connection. If, in the example in Figure 1, the CONNECT statement appeared only in the initialization data sets for nodes 1 and 2, the connection is private and node 3 cannot reach node 1. Because the CONNECT statement describing the node 1-to-node 2 connection does appear among the initialization statements of some of the other nodes in the network, in this example, the connection is known to the nodes that have the CONNECT statement.

Specifying the CONNECT statement places an entry describing the connection in the path manager routing tables.