Function

To add static network connections.

Parameters

MA|MEMBA|MEMBERA=membera

The member number at the NODEA end of the connection.

Default: The default is 1. The value for MEMBERA if NODEA is the local node must be a 1. If the member number is greater than a 1 for the local node, the command is rejected.

Note: Most supported NJE nodes require this parameter to be defaulted or set to 1. This parameter should only be used if the documentation for the NJE product on the node specified by NODEA= requires it. Improper specification of this field can cause portions of your NJE network to be unreachable. IBM® recommends that you do not specify this parameter, and allow it to default.

MB|MEMBB|MEMBERB=memberb

The member number at the NODEB end of the connection.

Default: The default is 1. The value for MEMBERB if NODEB is the local node must be a 1. If the member number is greater than a 1 for the local node, the command is rejected.

Note: Most supported NJE nodes require this parameter to be defaulted or set to 1. This parameter should only be used if the documentation for the NJE product on the node specified by NODEB= requires it. Improper specification of this field can cause portions of your NJE network to be unreachable. IBM recommends that you do not specify this parameter, and allow it to default.

NA|NODEA=nodea

Specifies the 1– to 8–alphanumeric or special ($, #, or @) character symbolic node name (xxxxxxxx) or node number (nnnn) at one end of the connection. The name must match the NAME= parameter of the NODE initialization statement for the referenced node. The node number must be less than the NODENUM= parameter of the NJEDEF statement.

Note: NODEA and NODEB may appear in any order when defining a static connection, that is NODEA does not have to be your node or the other end. When JES2 resolves the static connection, the order may be different than what was entered on the command when you issue a $DCONNECT. This is because the node with the smallest number will always be assigned to NODEA. The end result is the same.

NB|NODEB=nodeb

Specifies the 1– to 8–alphanumeric or special ($, #, or @) character symbolic node name (xxxxxxxx) or node number (nnnn) at one end of the connection. The name must match the NAME= parameter of the NODE initialization statement for the referenced node. The node number must be less than the NODENUM= parameter of the NJEDEF statement.

Note: NODEA and NODEB might appear in any order when defining a static connection, that is NODEA does not have to be your node or the other end. When JES2 resolves the static connection, the order may be different than what was entered on the command when you issue a $DCONNECT. This is because the node with the smallest number will always be assigned to NODEA. The end result is the same.

PATHMGR={No|RESET|Yes}

Indicates whether this connection supports path manager type protocols. PATHMGR=RESET indicates that the value of PATHMGR= should be reset to the default.

Default: The default depends on the specifications for the NODEA= and NODEB= parameters.

• If either node is defined as PATHMGR=NO, the default is PATHMGR=NO. You can sign on to JES3 or VM.
• If both nodes are defined as PATHMGR=YES, the default is PATHMGR=YES.

  Note: This static connection has a resistance of 30.

REST=rest

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

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.

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

Single Member. The values supplied for this command will be in effect for this member only.

Depending on your installation's setup, however, you might want 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 $HASP815 message is issued in response to this command.