Defining nodes using generics

You can minimize the number of statements needed to define your network by using generics to define your nodes. You use generics to define :

Common characteristics of all nodes
Unique characteristics for individual nodes
Unique characteristics for groups of nodes.

To clarify this point, study Figure 1 and its explanation immediately following.

Figure 1. Defining Nodes Using Generics

    NODE(*) REST=125
    NODE(1) NAME=WASH1,AUTH=(DEVICE=NO,NET=YES)
    NODE(2) NAME=WASH2,AUTH=(SYSTEM=NO,JOB=NO)
    NODE(3) NAME=WASH3,AUTH=(SYSTEM=NO,NET=YES),HOLD=JOBS
    NODE(4) NAME=NYORK1,AUTH=(JOB=NO,NET=YES)
    NODE(5) NAME=NYORK2,AUTH=(DEVICE=NO,SYSTEM=NO)
    ⋮
    NODE(WASH*) REST=250,AUTH=(JOB=NO)
    NODE(NYORK*) HOLD=JOBS

The NODE(*) statement initially assigns a resistance value of 125 as the default for all nodes (NODE(1) through NODE(32767)) during initialization statement processing.
When initialization processing completes, JES2 limits the set of affected nodes (1-32767) by the maximum specified in the NODENUM= parameter on the NJEDEF initialization statement.

Note: This might significantly elongate JES2 initialization processing. You should use a more realistic number such as NODE(1-500) rather than NODE(*).
Specific definitions for individual nodes (NODE(1) through NODE(5)) follow to add to or override the previous generic assignment statement.
The last two statements (NODE(WASH*) and NODE(NYORK*)) assign values for groups of nodes.
- The NODE(WASH*) statement overrides the values for REST= and AUTH= for all nodes whose names begin with WASH.
- The NODE(NYORK*) statement overrides the values for HOLD= for all nodes whose names begin with NYORK.
These values replace those previously defaulted or defined in previous generic statements.

Defining nodes in the network requires careful planning and coordination among participating installations to ensure that JES2 does not encounter duplicate node names. You must ensure that a name known to any node is reachable from all nodes.