APPC Subsystem on MPE/XL Node Manager's Guide (30294-90007)

Chapter 5 121
Managing the APPC Subsystem
Managing APPC Sessions
--------------------------------------
Independent LU Session Type : INDSESS1
--------------------------------------
Number of Active Sessions : 3
Number of Queued Session Requests : 0
Session Limits
Local LU SNA Node Remote LU Mode Maximum Current
-------- -------- ----------------- ------ ------- -------
INDLU1 AS400PU NET1.AS400LU1 MODE1 8 2
Session ID LFSID State LU Type TP ID
---------- ----- -------- ------- -----
26 0101 1 ACTIVE PRI 4425
28 0103 1 ACTIVE PRI 2215
29 0104 1 ACTIVE PRI 6924
To terminate all sessions of type INDSESS1, you issue the APPCCONTROL
SESSIONS command to reduce the session limit to 0:
:APPCCONTROL SESSIONS; STYPE=INDSESS1; LIMIT=0
This command terminates all active sessions of type INDSESS1.
Sessions are terminated with a shutdown type of QUIESCE, meaning
that all conversations on the affected sessions are allowed to end before
the sessions are terminated. A message is logged for each session that
is terminated.
NOTE
If, for some reason, the APPCCONTROL SESSIONS command fails to bring
down all the sessions you wish to terminate, you can use the
APPCCONTROL STOPSESSION command. The APPCCONTROL STOPSESSION
command is used to kill a session that is still active after you have tried
to terminate it with the APPCCONTROL SESSIONS command. The
APPCCONTROL STOPSESSION command terminates a session with a
StopType of KILL; that is, it terminates the session immediately,
without waiting for any conversation using the session to complete.
An APPC session can be terminated from the remote side. When the
remote system terminates a session, the APPC subsystem attempts to
reestablish it. The following is an example of the logging messages you
would see if this occurred:
APPC: Session stopped, Session ID=26, Reason=Host_Unbind (APPCLOG 7)
APPC: Session started, Session ID=26 (APPCLOG 6)