gtps2m1e | ACF/SNA Data Communications Reference |
The session manager is responsible for insuring that the underlying LU-LU
session needed for a conversation is available. When an ALLOCATE
request is issued, the session manager sends out a LOCATE/CDINIT to initiate
another session if there is no session active and bound or available for the
conversation, and the session limit has not been reached.
- Note:
- There is 1 exception to this: PU 2.1 secondary LU (SLU) thread
sessions cannot be activated from the TPF side.
If you want to initiate a session before issuing an ALLOCATE request, you
can use 1 of the following ways:
- The VTAM operator issues a VARY NET ACT LOGON command.
- Through the use of autologon at network definition for VTAM or
CICS. To define autologon in VTAM, code LOGAPPL on an
LU. To define autologon in CICS, code CONNECT=AUTO on the
DFHTCT statements.
- The end user (remote LU operator) can also initiate a session. The
procedures for this depends on the type of remote LU. See the
publications associated with the remote LU for details on these
procedures.
See IBM Systems Network Architecture Format and
Protocol Reference Manual: Architecture Logic for LU Type
6.2 for information about the LU 6.2 BIND command.
Sessions are terminated with an UNBIND command. Session termination
can be requested in the following ways:
- The VTAM operator issues a VARY NET INACT.
- The remote LU sends a LOGOFF or Terminate-Self command to its SSCP.
- The TPF operator issues a ZNETW INACT command.
- Note:
- If you inactivate a local TPF/APPC PLU that has SLU threads, only sessions
with the PLU are ended; there is no affect on any sessions with the SLU
threads.
- The TPF operator issues a ZNCNS RESET command.
- The TPF operator issues a ZNCNS CHANGE command to lower session
limits.
For details on the ZNETW and ZNCNS commands, see the "ACF/SNA
Communications Commands" in TPF
Operations.