| 
|  | » |  | 
 |  | Stops an 
LU-LU session without stopping the SNA node. | Syntax |  |  | 
| 
   SNACONTROL       STOPSESS;NODE=NodeName;LUNAME=LUName
                      [;TYPE=StopType]
 | 
| Use |  |  | 
SNACONTROL STOPSESS can be issued from a session, a job, 
a program, or in break.  Pressing BREAK has no effect on this 
command.| Parameters |  |  | 
NodeNameConditionally required.  The name of the active SNA node the LU-LU session is on.  The name 
can be up to eight alphanumeric characters long; the first character 
must be alphabetic. If only one SNA node is active, this parameter is optional:  If 
you do not include it, the specified LU-LU session on the active node 
is stopped.  If more than one node is active, this parameter 
is required:  If you do not include it, an error message is displayed 
and no LU-LU session is stopped.LUNameRequired.  The name of the LU whose session you want to stop.  The name can be up 
to eight alphanumeric characters long; the first character must be 
alphabetic.StopTypeHow SNA Transport is to stop the session: P = (Protocol) 
SNA Transport notifies the SNA services that it is stopping the specified 
LU.  Each service interrupts sending and receiving all active data 
sets for the LU-LU session and tries to stop the specified LU.Q = (Quiesce) 
The session is stopped in an orderly way.  SNA Transport notifies 
the SNA services that it is stopping the specified LU.  Each service 
completes sending and receiving all active data sets in the LU-LU 
session.  Once the session is stopped, a logging message specifying 
that the LU-LU session has terminated is generated.
Default: Q
| Example |  |  | 
SNACONTROL STOPSESS;NODE=ALPHA;LUNAME=LU1 The LU-LU session for LU1 on node ALPHA is to be stopped in an orderly 
way (a quiesce).  A quiesce is done because no StopType 
was specified.  |