NODE(xxxxxxxx) - Define a Network Node to JES2

The NODE(xxxxxxxx) statement defines each node or a range of nodes. The subscript (nnnn) can specify:
  • A specific node with a numeric identifier (1-32767), as specified by the NODENUM= parameter on the NJEDEF statement), for example, NODE(105).
  • A range of nodes with a generic numeric identifier in the form NODE(x-*), for example, NODE(105-*).
  • A specific node with a symbolic identifier in the form xxxxxxxx, for example, NODE(POKIPSY1). This must be related to a NAME= parameter on a previous NODE(xxxxxxxx) statement.
  • A range of nodes with a generic symbolic identifier in the form jx*, for example, NODE(POK*).
  • All nodes in the form NODE(*). This defines all nodes from 1 to the NODENUM= specification on the NJEDEF initialization statement. Using the form NODE(*) causes JES2 to scan for 32767 nodes, regardless of the number previously defined. Using this option does not create definitions of additional nodes (that is, above the NODENUM= specification on the NJEDEF initialization statement), but can significantly increase the processing time that JES2 takes to process this initialization statement.
Note:
  1. If the node being defined is the same as that specified by the OWNNODE= parameter on the NJEDEF statement (the NODE(xxxxxxxx) statement is for the node that is being initialized, not for another node), the only useful specifications are the NAME= and PASSWORD= parameters. When one member signs on to another, the name and password(s) are used in the signon sequence such that the other member can verify the acceptability of the member signing on.
  2. Before defining a node name that starts with a numeric character, ensure that all nodes in your network support node names that start with numeric characters, that is, the nodes are at JES2 SP5.1 or higher.