z/OS JES2 Initialization and Tuning Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Starting SNA dynamic connections

z/OS JES2 Initialization and Tuning Guide
SA32-0991-00

For an SNA NJE session, you must define a logical SNA line; that is, you must have added UNIT=SNA on the LINE(nnnn) initialization statement. If the line is not dedicated, (no LINE= parameter specified on either the NODE(nnnn) or APPL(avvvvvvv) initialization statement), an operator must enter a $S LINE(nnnn) command to start the line before attempting to establish any SNA connections.

After the line starts, an operator at either NJE node issues a start networking ($S N) command to initiate an SNA NJE application-to-application session. When entering the $S N command, the operator can specify one of two names to identify the other node:
  • The unique application name (on the A= parameter) by which VTAM® knows JES2 at the other end. (The JES2 LOGON(1) initialization statement at the other node uses the application name to identify JES2 as a cross-domain resource to VTAM.)
  • The node name if only one application exists at that node.
If a dedicated line exists but is drained, it will be automatically started by the $S N command. For SNA application-to-application sessions, JES2 invokes the path manager after VTAM establishes the SNA session.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014