z/OS JES2 Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$S N - Start node communication on a TCP/IP line

z/OS JES2 Commands
SA32-0990-00

Function

To start a TCP/IP application-to-application session with another node and to automatically start dedicated lines.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-$S--N--+-------------+--+----------------------+------------->
          '-,LINE--nnnn-'  '-,SOCKET=--socketname-'   

>--+---------------+-------------------------------------------><
   '-,N=--nodename-'   

Parameters

N
Identifies this as a start networking command.
LINEnnnn
Specifies a logical TCP/IP line (UNIT=TCP) to be used by this network connection. If you omit this parameter, a TCP/IP logical line will be selected from a pool of available or idle TCP/IP lines. At least one TCP/IP line must be available to establish a TCP/IP connection. If a line has been dedicated to this socket (LINE=on the SOCKET statement) or to this node (LINE= on the NODE statement), it will be automatically started and a TCP/IP connection will be established.
S=|SOCKET=
Specifies the name of a TCP/IP socket with which a NJE connection should be initiated.
N=nodename
1-8 alphanumeric or special character name ($, #, or @) of the node can be used to start networking. Use a socket associated with the node.

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. $T NODE(nnnn) sets the command authority for a node.

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.

Processing Considerations

When processing the $SN,N=nodename command, JES2 gives priority to dedicated lines, and to TCP/IP over SNA/VTAM.

Scope

Single system. This command will be in effect for this member only. There is no need to have this command issued to all members of the MAS.

Messages

The $HASP000 message indicates the command was accepted.

The $HASP200 message indicates the target node name is started on the specified line.

Examples

         ┌────                  └────
  NJEDEF OWNNODE=1                    NJEDEF OWNNODE=2
  NODE(1) NAME=POK                    NODE(1) NAME=POK,
  NODE(2) NAME=WSC,                           LINE=21
          LINE=20                     NODE(2) NAME=WSC
  LINE20  UNIT=TCP                    LINE21  UNIT=TCP
  SOCKET(POK) NODE=1                  SOCKET(POK) NODE=1,
  SOCKET(WSC) NODE=2,                   IPADDR=POK.IBM.COM,
    IPADDR=WSC.IBM.COM,                 PORT=175
    PORT=175                          SOCKET(WSC) NODE=2
  NETSRV1 SOCKET=POK                  NETSRV1 SOCKET=WSC
  -------------------------------------------------------

  $SNETSRV1                           ...
  ...                                 $SNETSRV1
  $SN,S=WSC                           ...

At NODE(POK), $SN searches for a SOCKET that is assigned to node 2. NODE(WSC) points to LINE20, which is automatically started. The node password is automatically obtained from NODE(WSC).

At NODE(WSC), HASPTCP searches for a SOCKET assigned to node 1. NODE(POK) points to LINE21, which is automatically started.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014