Naming restrictions

In all communications with other nodes, a node uses its node name (the symbolic name, not the number). These communications include network connection control signon records. When verifying a signon, the receiving node checks the name received against its list of valid nodes.

Installations should specify both node names and numbers consistently, or risk having operators receive confusing JES2 operational messages. Because JES2 messages often display only the node number, an operator could be confused by the situation in Table 1, where N1 is NODEA at one node and NODEB at another.

Table 1. Confusing JES2 Node Naming Conventions To Avoid.
`Node A`	`Node B`
`NJEDEF OWNNODE=1 NODE(1) NAME=NODEA,... NODE(2) NAME=NODEB,...`	`NJEDEF OWNNODE=1 NODE(1) NAME=NODEB,... NODE(2) NAME=NODEA,...`

JES2 propagates NODE(nnnn) initialization statement names throughout an NJE network, so these names must be unique throughout the network.