Use symbolic node names (rather than node numbers) to make individual nodes in your network easier to remember. For example, Honolulu is more memorable to you and your operators than N4358. However, it is not a good idea to use an unqualified city name (for example, DALLAS) because the city name could cause duplicate node name problems when you join two networks together. You should always use some manner of qualification (such as DALLAS1) when naming your nodes. Specify the names you want to give to each node in the NAME= parameter of the NODE(nnnn) initialization statement. For example, NODE(1) corresponds to POKIPSY1 in the following statement:

    NODE(1)    NAME=POKIPSY1

Any following initialization statements or commands can then see the name, rather than the number of the node, for example: This eliminates the need to remember the association between NODE(1) and the symbolic name, POKIPSY1. Furthermore, for display purposes ($D NODE) or for changing NODE characteristics ($T NODE), you can specify the NODE subscript as a generic form. For example, NODE(POK*) indicates all nodes with a name beginning with POK.

    $T  NODE(POKIPSY1),AUTH=(JOB=NO)

The symbolic name assigned to a node through the NAME= parameter on the NODE(nnnn) statement should not be of the form NxRx, or Nxxx, which JES2 might incorrectly resolve as a different node.