Parameter Description for NODE(xxxxxxxx)

AUTH=

Specifies the level of command authority for this node in relation to another node.

Note: This parameter has no effect when the associated resource class and profile in RACF® 1.9 or higher are active. For more information on JES2 security, see z/OS JES2 Initialization and Tuning Guide.

NET=

Specifies the node's network authority.

Yes: Specifies that the node has the command authority of locally attached consoles.
No: Specifies that this node can only enter commands that affect devices (assuming DEVICE=Yes) and jobs (assuming JOBS=Yes). If all AUTH subparameters are No, the node being defined can enter only display commands to this member (the defining node).

Device=

Specifies this node's authority over devices on this member.

Yes: Specifies that the node has command authority to affect devices on this member.
No: Specifies that the node cannot enter commands that affect devices on this member.

Job=

Specifies this node's authority over jobs on this member.

Yes: Specifies that the node can enter commands that affect jobs.
No: Specifies that the node cannot enter commands that affect jobs on this member.

System=

Specifies this node's authority over all members at the node being defined. If NET=No, this parameter has no effect.

Yes: Specifies that the node can enter commands that affect system functions on these members.
No: Specifies that the node cannot enter commands that affect system functions.

Modification: $T NODE(xxxxxxxx) operator command.

COMPACT= nn|0

Specifies the number (nn) of the compaction table to be used for outbound compaction in communicating with this node. The compaction table number must be in the range of 0 to 99, where 0 denotes no compaction.

The value specified here will be used as a default if no value for COMPACT is specified on the APPL(jxxxxxxx) initialization statement for an SNA NJE networking node.

This parameter defaults to 0, indicating no compaction.

Modification: $T NODE(xxxxxxxx) operator command.

CONNECT= (YES|NO,interval)

Specifies whether NJE connections, which specify CONNECT=DEFAULT on the APPL, LINE, or SOCKET statements associated with this node, are automatically attempted. The interval is the approximate time (in minutes) between attempted connections. The valid range for interval is 0-1440; the default value is 0. A value of 0 indicates that the default interval (from NJEDEF CONNECT=) is used. The default CONNECT value is NO.

Note: This parameter starts all connections that point to the node, through LINE NODE=, APPL NODE=, or SOCKET NODE=, plus the line that NODE(n) LINE= points to if any.

DIRECT=YES|NO

Specifies whether the node must be directly attached:

YES: Indicates that only direct connections to this node will be considered when computing path information.
NO: Indicates that the node can be reached either through direct or indirect paths. For example, store-and forward.

DIRECT has MAS scope. The values can be changed on any start other than a hot start, and will affect all MAS members regardless of whether the node is active or inactive.

ENDNODE=Yes|No

Specifies whether (Yes) or not (No) the node is to be eligible for use in store-and-forward operations. This parameter has MAS scope.

Yes

Local node: If you are defining your node (the local node) and you do not want the node to be eligible for use in store-and-forward operations, code ENDNODE=Yes. This ensures that path manager connect records are not sent from your node to adjacent nodes.

Where possible, IBM suggests that other nodes also specify ENDNODE=Yes on their initialization statements for your node. If all nodes in the network define your node as an end node, the possibility of your node being used for store-and-forward operations is reduced.

Non-local node: If you are defining a remote node and the installation personnel at that node have defined the node as an end node, code ENDNODE=Yes.

No

Local node: If you are defining your node (the local node) and the node is to be eligible for use in store-and-forward operations, code ENDNODE=No or omit the parameter.

If you specify ENDNODE=No for this node, IBM suggests that other nodes specify ENDNODE=No on their initialization statements for your node.

Attention: If your node provides the only gateway into a subnet, IBM suggests that you define your node as eligible for store-and-forward operations. To do otherwise prevents other nodes from communicating with the subnet.

Non-Local node: If you are defining a remote node and the installation personnel at that node have defined the node as eligible for store-and-forward operations, code ENDNODE=NO or omit the parameter.

Modification: To modify the ENDNODE= specification for the local node, you must perform a hot start. To modify the ENDNODE= specification for other nodes, use the $T NODE(xxxxxxxx) operator command. The values can be changed on any start other than a hot start, and will affect all MAS members regardless of whether the node is active or inactive.

HOLD=JOBS|NONE

HOLD=JOBS specifies that the node, as specified as OWNNODE on the NJEDEF statement will hold jobs received from the specified node(s). HOLD=NONE specifies received jobs will not be held.

Modification: $T NODE(xxxxxxxx) operator command.

LINE=nnnn

Specifies a line to be dedicated to the NJE session associated with this node. Range is 0-65535.

Note: If there are multiple SNA paths to this node, use the LINE= parameter on the APPL initialization statement; if there are multiple TCP/IP paths to this node, use the LINE=parameter on the SOCKET initialization statement.

Default: 0 (No line is dedicated.)

Modification: $T NODE(xxxxxxxx) operator command, if the node is not active.

LOGMODE=avvvvvvv

Specifies the logon mode table entry name for this application. This name will determine which entry in the VTAM® application logon mode table is to be used to provide a set of session parameters for the application program if the program participates as the secondary end of a session. This parameter is valid only for NJE applications. The name specified should follow the VTAM naming conventions for a logon mode table entry name. See z/OS V2R1.0 Communications Server: SNA Programming for more information about the logon mode table.

The default value of the name are blanks, and VTAM defaults are used for the session parameters.

Modification: $T NODE(xxxxxxxx) operator command, if the node is not active.

LOGON=nn

Specifies the number of the logon DCT to be used in communication with this node.

NAME=xxxxxxxx

Specifies the 1- to 8-character name that symbolically defines the node. A DESTID statement defining this name is not required.

Restrictions:If the XCFGRPNM parameter is not coded on the MASDEF statement, the node name should follow the XCF naming conventions. To avoid using the names IBM uses for its XCF groups, do not begin names with the letters A through I or the character string SYS. Also, do not use the name UNDESIG, which is reserved for use by the system programmer in your installation.

Note:

When using the spool offload facility, be certain that the node name of the offloaded member is known to the reloading member. If these names do not match, unpredictable routing of jobs and SYSOUT can occur on the reloading member. Any unresolved routing will result in SYSOUT or jobs executing and printing locally.
If a non-numeric subscript is specified for NODE, that is NODE(xxxxxxxx) or NODE(xx*), the subscript must match the specification on this parameter.
You should not use RMTnnnn, RMnnnn and Rnnnn as symbolic names.
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 values.
When naming a node, avoid 1- to 4-digit number such as ‘3’ and ‘234’. This can cause confusion when the name is used in commands or displayed in messages. Consider the following initialization statements and series of commands:
```
NODE(3)   NAME=246
NODE(246) NAME=POKIPSY
```
If you enter:
```
$T NODE(3)
```
JES2 modifies the third node (NAME=246).
If you enter:
```
$T NODE(POKIPSY)
```
JES2 modifies the 246th node (NAME=POKIPSY).
However, if you enter:
```
$T NODE(246)
```
it might not be obvious that JES2 modifies the third node (NODE(3) NAME=246), not NODE(246) NAME=POKIPSY.
Therefore, if you must use 1- to 4-digit names, to reduce any possibly of confusion, pad the number on the left with 0s. The above example becomes:
```
NODE(3)   NAME=00000246
NODE(246) NAME=POKIPSY
```
Now $T NODE(246) modifies the 246th node (NODE(246) NAME=POKIPSY), and $T NODE(00000246) modifies the third node (NODE(3) NAME=00000246).

This parameter has MAS scope.

The default value of this parameter is Nnnnn where nnnn is the node number.

Modification: $T NODE(nnnn) operator command. If you modify this parameter value and then restart JES2 with a hot start, the parameter value in effect before termination will be used. This specification cannot be changed if the NODE(xxxxxxxx) or NODE(xx*) form of the NODE statement is to be used. The values can be changed on any start other than a hot start, and affect all MAS members regardless of whether the node is active or inactive.

NETSRV=nnn

Specifies the device number of the NETSRV that is to be used to establish a TCP/IP NJE connection to this node.

Default 0 (no NETSRV is to be dedicated).

Modification: Operator command.

Password=([SEND=word1,]VERify=word2) | word

Specifies passwords for verification each time one node signs on to another. There are two ways of specifying the parameter:

Password = ([SEND=word1,]VERify=word2) allows you to specify unique passwords to be used between nodes that communicate with each other in the network. This method provides enhanced security for the transmission of information between nodes, and is the preferable way of specifying Password=.
Password=word allows a node to send a common password to all nodes with which it might communicate. Although it is recommended that you define all nodes using Password=(SEND=word1,VERify=word2), the Password=word method provides compatibility with previous releases of JES2.

Detailed descriptions for both methods follow.

Password=([SEND=word1,]VERify=word2)

Use Password=(SEND=word1,VERify=word2) to specify unique passwords between nodes in the network.

SEND=word1: Specifies a unique 1- to 8-character password that will be sent to the node by OWNNODE when it is signing on to the node, to verify that OWNNODE is the correct node.
VERify=word2: Specifies the 1- to 8-character password that OWNNODE will expect back from the node.

Password=word

Specifies a 1- to 8-character password that is to be used when the node is signing on to any other node.

Note:

If all nodes in your network use the Password=(SEND=word1,VERify=word2) method of password verification, it is unnecessary to include this Password= parameter on the NODE(xxxxxxxx) initialization statement for OWNNODE in this initialization stream. However, if some nodes use the Password=(SEND=word1,VERify=word2) specification and others use the Password=word specification, you must include a PASSWORD=(VERify=word2) specification for the OWNNODE.
Using Password=word is similar to specifying Password=(VERify=word2) for OWNNODE. The result is that OWNNODE will send the same password to all nodes to which it may sign on.
If both Password specifications are omitted, no password verification of the node will be performed unless the operator sets a password through the JES2 $T N command.
To prevent disclosing the passwords, protect the data set containing the initialization statements. If RACF 1.9 or higher is used, protection can be provided by specifying UACC=NONE for the data set.
Be certain to record the passwords in effect, because no facility exists to display the current value.

This parameter has no default.

Modification: $T NODE(xxxxxxxx) operator command.

PATHMGR=Yes | No

Specifies whether (Yes) or not (No) connection records should be sent to the directly adjacent node defined by this statement. You must specify PATHMGR=No when connecting to adjacent non-JES2 nodes. A CONNECT statement is not necessary for connecting to adjacent non-JES2 nodes. This parameter has MAS scope.

Modification: $T NODE(xxxxxxxx) operator command, if the node is not active. The values can be changed on any start other than a hot start, and will affect all MAS members regardless of whether the node is active or inactive.

PENCRYPT=Yes|No

Specifies whether (Yes) or not (No) this node supports password encryption.

If PENCRYPT=Yes, JES2 encrypts the password for any job sent across the network to this node. The encryption scheme JES2 uses is the data encryption system (DES) that exists in RACF. If the destination node's security product can not interpret passwords using this scheme, the job(s) will fail.

If PENCRYPT=No, JES2 does not encrypt the password for jobs sent across the network to this node.

Modification: $T NODE(xxxxxxxx) operator command.

PRIVATE=Yes | No

Specifies whether or not the information about the connection between the local node and the directly adjacent node defined by this statement is to be kept private; that is, the information is only known to this node and the directly adjacent node. Yes specifies that the information is not to be sent to other nodes, No specifies that the information is sent to other nodes. The information about the connection is always sent to other members of this MAS. This parameter is ignored if the node is not a directly adjacent node. This parameter has MAS scope.

Modification: $T NODE(xxxxxxxx) operator command, if the node is not active. The values can be changed on any start other than a hot start, and will affect all MAS members regardless of whether the node is active or inactive.

RECeive=JOBS|SYSOUT|NONE|BOTH

Specifies what the node, as specified as OWNNODE= on the NJEDEF statement, will receive from the specified adjacent node.

JOBS: Indicates that OWNNODE can only receive JOBS from the specified node(s).
SYSOUT: Indicates that OWNNODE can only receive SYSOUT from the specified node(s).
NONE: Indicates that OWNNODE will accept no data (JOBS or SYSOUT) from the specified node(s).
BOTH: Indicates that OWNNODE will accept both JOBS and SYSOUT from the specified node(s).

For example, NODE(5) REC=BOTH allows OWNNODE to accept both JOBS and SYSOUT from NODE5

Modification: $T NODE(xxxxxxxx) operator command.

REST=nnnn|0

Specifies an integer (0-2000) that represents the resistance rating of the connection as viewed by the installation manager and coordinated with other installations. If the node is specified as PATHMGR=NO, and no CONNECT statement is specified for this node, this value will be the total resistance of the direct connection to this node plus the resistance of the node. See z/OS JES2 Initialization and Tuning Guide for details concerning resistance selection. The value specified here will be used as a default if no APPL is defined for a SNA NJE networking node (that is, the APPL is dynamically defined). For BSC, node REST= is not used. LINE resistance is used instead. For BSC, this value is specified on the REST= parameter of the LINEnnnn statement.

Modification: $T NODE(xxxxxxxx) operator command.

SENTREST=ACCEPT|IGNORE

The total resistance of a connection is comprised of the partial resistance of the local node plus the partial resistance of the node to which you are making a connection.

When a connection is established between the local node and another node (that is, the node you specify on this NODE(xxxxxxxx) statement), SENTREST=ACCEPT specifies that the partial resistance sent to the local node during signon processing is to be added to the partial resistance calculated by the local node to determine the total resistance of the connection. SENTREST=IGNORE specifies that only the partial resistance calculated at the local node is to be used to calculate the total resistance of the connection. The partial resistance sent by the other node is ignored. This keyword only applies if PATHMGR=NO.

This keyword is useful when the node to which the connection is being made cannot control the resistance being sent during signon processing.

Modification: $T NODE(xxxxxxxx) operator command.

SIGNON=SECURE | COMPAT

Specifies the type of signon security to be used when NJE connections to this node are established:

COMPAT: Specifies that node and line passwords, where applicable, are to be exchanged and verified by the NJE signon process.
SECURE: Specifies that encrypted session keys are to be exchanged rather than node and line passwords.

Modification: $TNODE(nnn) operator command.

Note: For nodes connected through BSC, the N= parameter MUST be specified on the $SN command for a secure signon to be processed.

SUBnet=xxxxxxxx

Specifies the name of the subnet in which this node belongs. Connection records between two nodes in the same subnet are not passed between nodes outside that subnet.

This parameter has no default. It has MAS scope.

Modification: $T NODE(xxxxxxxx) operator command. The values can be changed on any start other than a hot start, and will affect all MAS members regardless of whether the node is active or inactive.

TRace= Yes | No

Specifies whether network connect control (NCC) records to and from the direct connection to the specified member of this node should be traced (trace IDs 21 through 24).

Modification: $T NODE(xxxxxxxx) operator command.

TRAnsmit=JOBS|SYSOUT|NONE|BOTH

Specifies what the node, as specified as OWNNODE= on the NJEDEF statement, will transmit to the specified adjacent node.

JOBS: Indicates that OWNNODE can only transmit JOBS to the specified node(s).
SYSOUT: Indicates that OWNNODE can only transmit SYSOUT to the specified node(s).
NONE: Indicates that OWNNODE will transmit no data (JOBS or SYSOUT) to the specified node(s).
BOTH: Indicates that OWNNODE will transmit both JOBS and SYSOUT to the specified node(s).

For example, NODE(5) TRA=BOTH allows OWNNODE to transmit both JOBS and SYSOUT to NODE5.

Modification: $T NODE(xxxxxxxx) operator command.