Function

To set or reset the characteristics of the specified node.

One or more parameters on this command accept wild cards. Parameter descriptions will note that.

Parameters

(nnnnn|xxxxxxxx|xx*|*)

The subscript defining the node(s) affected by this command.

The subscript can specify:

• A numeric value (1-32767), as specified by the NODENUM parameter on the NJEDEF initialization statement), for example NODE(105).
  Note: For information about specifying a range of values for the nnnn subscript, see Command syntax conventions.
• The name of the 1– to 8–alphanumeric or special ($, #, or @) character node (xxxxxxxx) as specified by the NAME parameter on the NODE(nnnn) initialization statement (for example, NODE[POKBLDG1]). This name must be the same for all members of a MAS configuration.
• Wild cards to specify a generic symbolic range (for example, POK* implies all defined nodes whose names begin with POK) or a generic value (for example, * implies node 1 to the highest numbered node as specified by the NODENUM parameter on the NJEDEF initialization statement). For example, NODE(*). See Using wildcards for additional information.

Note: To change the name of the node (NAME=), you must specify a numeric value as the subscript.

Scope: Single Member.

AUTH=([Device=No|Yes[]Job=No|Yes] [Net=No|Yes][System=No|Yes])

Specifies the types of commands that the indicated node has authority to issue to the local node.

Device={No|Yes}

If Device=Y and Net=Y is also specified, the node has authority to issue device commands to the local node.

If Device=N is specified, the node does not have device command authority.

Job={No|Yes}

If Job=Y and Net=Y is also specified, the node has authority to issue job-related commands to the local node. If Job=Y and Net=N is specified, the node can control only those jobs on the local node that it owns.

Note: A node is considered to own a job if the job originated at that node or if the job's default print and/or punch output is for that node.

If Device=N is specified, the node does not have job command authority.

Net={No|Yes}

If Net=Y is specified, the node has authority to issue all types of commands from its system console to the local node (except for those commands that are always prohibited when they originate from another node).

If Net=N is specified, the node can control only those jobs on the local node that it owns (providing Job=Y is also specified).

Note: A node is considered to own a job if the job originated at that node or if the job's default print and/or punch output is for that node.

System={No|Yes}

If System=Y is specified and Net=Y is also specified, the node has authority to issue system commands to the local node.

If System=N is specified, the node does not have system command authority.

Note:

1. If you specify N for every AUTH= subparameter, the indicated node has no specific command authority, and the local node honors only those few commands requiring no authority (for example, display commands).
2. Network authority requires having system, job, or device authority in addition to network authority to have system, job, or device commands take affect at another node.
3. In a multi-access spool configuration, you should enter the $T NODE(nnnn),AUTH= command on each member of the node because each member maintains its own version of the node information table.

Scope: Single Member.

ADJACENT=YES|NO (Selection limiting keyword)

Specifies whether the node is currently directly attached.

Scope: Single Member.

CONNECT=(Yes|No,interval)

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

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 may be reached either through direct or indirect (for example, store and forward) paths.

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.

Scope: MAS-Wide.

COMPACT=nn

The compaction table number (0-99) used for outbound compaction in communicating with the specified node. Zero denotes no compaction.

Scope: Single Member.

ENDNODE={No|Yes}

Specifies whether the node is to be considered eligible for use in store-and-forward operations.

Yes

Indicates that the node is to be considered ineligible for use in store-and-forward operations. ENDNODE 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.

By specifying ENDNODE=YES for a local node, you ensure that path manager connect records are not sent from your node to adjacent nodes.

No

Indicates that the node is to be considered eligible for use in store-and-forward operations.

Scope: MAS-Wide.

HOLD={JOBS|NONE}

Specifies whether the local node holds jobs (HOLD=JOBS) or does not hold jobs (HOLD=NONE) received from the specified node.

Scope: Single Member.

LINE=nnnn

Specifies a line to be dedicated to the NJE session associated with this node. The subscript is specified as a numeric value (1-65535).

Scope: Single Member.

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.

Scope: Single Member.

LOGON=logon

Specifies the number (1-999) of the local LOGON DCT which should be used when specifying connections to the application. The default value of 0 indicates that the LOGON DCT defined with the lowest number is to be used.

Scope: Single Member.

NAME=xxxxxxxx | name | number | local

Specifies the 1 to 8 alphanumeric or special ($, #, or @) characters that symbolically defines the node. A DEStid initialization statement defining this name is not required. NAME 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. The name of any active node, including the local node, may be modified if a symbolic subscript is used.

Note:

1. To change the name of the node, if you specify a numeric value as the subscript, the node must not be active (connected to the local node). No static connections involving that node may exist, nor any connections with a RESTMAX state. However, if you specify a symbolic value as the subscript, JES2 considers this change a simple renaming of the node and will allow the change even if the node is active.

   In order to make the node inactive, issue the command $D CONNECT, NA=oldname, STATIC=YES to determine the connections. If they exist, use the $DEL CONNECT command to remove them, and then retry the $T NODE command.

   If you receive the $HASP003 error message, then check for RESTMAX connections by issuing the command:$D CONNECT, NA=oldname, STATE=RESTMAX Note these connections, then INOP the lines to the nodes that are causing the RESTMAX state condition to exist with the command: $ELNEx If too many of these connections exist, then you may find it prudent to shutdown ALL lines by issuing the command: $ELNEx(*) or, HOTSTART JES2 and effectively shutdown this NJE node.

   Now that the node is fully inactive, proceed with the command: $TNODE(xx),NAME=newname $TDESTID(oldname), DEST=oldname. In order for the node to become inactive, these commands need to be issued on all members of the MAS.

2. If you issue a $T NODE to change the name of an existing node, you must first issue a $T DESTID command specifying the new node number. All old node names remain on the system as destids until the member is warm started.
3. When using the spool offload facility, be certain that the node name of the offloaded system is known to the reloading system. If these names do not match, unpredictable routing of jobs and SYSOUT data can occur on the reloading system. ANY unresolved routing results in jobs or SYSOUT data executing or printing locally.
4. $T of nodename can be used if the NODE(nnnn) to be altered is OWNNODE, and all members are at least z/OS® 1.7 and NITCs are in the checkpoint.
5. If any inactive connections involving this node exist, they will be deleted to avoid sending erroneous information about the new node name into the network.
6. 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.
7. When naming a node, avoid names that consist only of 1– to 4–digit numbers (for example, NAME=3 or NAME=246). This can cause confusion when the name is used in commands or displayed in messages.

   To reduce any possibility of confusion if you must use 1– to 4–digit numbers for the name, pad the name to the left with zeros (for example, NAME=00000246).

   Using the following initialization statements, the command examples below help you to understand the effect of specifying a name that consists of four or less digits.

   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).

   If you enter: $T NODE(246)

   JES2 modifies the third node (NODE(3) NAME=246), not NODE(246) NAME=POKIPSY.

8. To add back a member that was in the MAS before the node name change, you also should update XCFGRPNM to the new node name on MASDEF on a warm start.

name

Can be done anytime.

number

Can only be done when no MAS member has an active connection to the node.

local

Is allowed.

Scope: MAS-Wide.

NETSRV=

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

Default: 0 (no NETSRV is to be dedicated).

Scope: Single Member.

OWNNODE=YES|NO (Selection limiting keyword)

Specifies whether the node is the local node.

Scope: Single Member.

Password=[SEND=xxxxxxxx|[VERify=xxxxxxxx]

If you specify both SEND and VERify, use a comma to separate the subparameters, and enclose them in parenthesis.

SEND

The 1 to 8 character password sent to a node by an NJE connection.

VERify

The 1 to 8 character password received from a node by an NJE connection.

Note:

1. If the specified node is equal to the value of the OWNNODE parameter on the NJEDEF statement, the password is transmitted to other systems so that the system authorization may be verified.
2. If you specify a null password (P=VER=, SEND= or both), JES2 deletes the previously assigned password.
3. Be certain to make a note of the password assigned because there is no facility for displaying the current passwords.

Scope: Single Member.

PATHMGR={No|Yes}

Indicates whether NCC records relevant to the path manager should be sent to this node. If the node is not a directly adjacent node, this parameter is not used. PATHMGR 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.

NO

Indicates that Reset (“L”), Concurrence (“K”), Add (“M”), and Subtract (“N”) NCC records are not sent to this adjacent node.

YES

Indicates that all relevant NCC records are passed to this adjacent node.

Note: If you specify PATHMGR=, the connection must be inactive.

Scope: MAS-Wide.

PENCRYPT={No|Yes}

Specifies whether passwords are to be encrypted for jobs destined to the specified node.

Scope: Single Member.

PRIVATE={No|Yes}

Indicates whether the connection between this node and an adjacent node is broadcast to the rest of the network. This parameter is not used if the node is not a directly adjacent node. PRIVATE 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.

NO

Indicates that the connection is considered public; Any Add (“M”) and Subtract (“N”) records for this connection are broadcast to all adjacent path manager nodes.

YES

Indicates that the connection is considered private; Any Add (“M”) and Subtract (“N”) records for this connection are not broadcast to adjacent nodes.

Scope: MAS-Wide.

RECeive={BOTH|JOBS|NONE|SYSOUT}

Specifies what the local node (as specified by the OWNNODE parameter on the NJEDEF initialization statement) receives from the specified node.

BOTH

The local node receives both jobs and SYSOUT data from the specified node.

JOBS

The local node receives only jobs from the specified node.

NONE

The local node does not receive any data from the specified node.

SYSOUT

The local node receives only SYSOUT data from the specified node.

Scope: Single Member.

REST=nnnn

An integer (0-2000) that represents the resistance rating of the connection as viewed by the installation manager and coordinated with other installations. See z/OS JES2 Initialization and Tuning Guide, SA32-0991 for details about selecting resistances.

Default: 0. Note that, although 0 is the default, it cannot be specified.

Scope: Single Member.

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(nnnn) 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 being connected to, cannot control the resistance being sent during signon processing.

Scope: Single Member.

SIGNON=

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.

Scope: Single Member.

SUBnet=xxxxxxxx

Specifies the 1– to 8–alphanumeric or special ($, #, or @) character name of the subnet that should include this node. Information about connections between two nodes in the same subnet are not passed between nodes outside that subnet. SUBnet 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.

Scope: MAS-Wide.

TRace={No|Yes}

Specifies whether NCC records to and from the direct connection to the specified node should be traced.

Tracing is activated if trace IDs 21, 22, 23, and 24 are currently enabled.

NO

Indicates that trace records are not to be written

YES

Indicates that trace records are to be written

Scope: Single Member.

TRAnsmit={BOTH|JOBS|NONE|SYSOUT}

Specifies what type of data the local node (as specified by the OWNNODE parameter on the NJEDEF initialization statement) transmits to the specified adjacentnode.

BOTH

The local node transmits both jobs and SYSOUT data to the specified node.

JOBS

The local node transmits only jobs to the specified node.

NONE

The local node does not transmit any data to the specified node.

SYSOUT

The local node transmits only SYSOUT data to the specified node.

Scope: Single Member.

Authority Required

This command requires system authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS™ system command group is assigned. The $T INTRDR command sets the command authority for internal readers.

This command requires control security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991.

Scope

The scope of this command varies by parameter. See the description of each parameter for its scope.

The values supplied for some parameters on this command will be in effect across the entire MAS while the values supplied for other parameters will be in effect for this member only.

Depending on your installation's setup, you might want the parameters for this command to be applied to all members of the MAS (to ensure a consistent environment across the MAS). If so, you can use the MVS ROUTE *ALL command to issue this command to all active members (if the JES2 command character is the same on all members). See z/OS MVS System Commands, SA38-0666 for more information on using the ROUTE *ALL command.

Messages

The $HASP826 message displays the current values of all the parameters on the NODE(nnnn) initialization statement.

JES2 changes the command authorities for all nodes whose names begin with POK (in this case, node 1). These nodes are authorized to issue job-related commands to the local node, but they cannot affect local devices. The local node now transmits both jobs and SYSOUT data to node 1. The STATUS= parameter shows the individual node's connection status with the local node.