SNAX/APC Configuration and Management Manual

Objects for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
7-17
Considerations for Dynamically-Added and Parallel-
Session PTNR-MODE Objects
In addition, a set of SNA-defined PTNR-MODEs will be added to the PTNR-LU. These
objects are discussed in detail next.
Immediately after these objects are added, the PTNR-LU and the default SNASVCMG
PTNR-MODE will be brought up to the STARTED state, and the BIND request will be
processed. The reset of the SNA-defined PTNR-MODEs will be brought up through the
following subsequent CNOS operations.
These dynamic objects will be brought down to the STOPPED state and removed from
the local LU after all of the subordinate sessions are terminated.
The SNA-defined PTNR-MODE Objects
Several PTNR-MODE objects representing representing the SNA-defined mode names
will be automatically added to a PTNR-LU object if the following conditions are met:
•
local LU supports DYNAMIC functions
•
local LU is a parallel-session LU (MAXSESSION > 1)
•
partner LU is also a parallel-session LU (with PARALLEL-SESSION-LU set to
YES)
These PTNR-MODE objects are:
•
SNASVCMG PTNR-MODE
$<apc-process>.<local-LU>.<partner-LU>.“SNASVCMG” is the object name of the
SNASVCMG PTNR-MODE in a SNAX/APC subsystem. It is architected for the
use of the CNOS operation, and has been implemented in SNAX/APC.
•
A default PTNR-MODE
$<apc-process>.<local-LU>.<partner-LU>.“#DEFAULT” is the object name of the
default PTNR-MODE in a SNAX/APC subsystem. It could be used by any
application transaction programs (ATP). It has the following default attribute
values:
MODENAME = “ ” (eight blanks)
DEFAULTMAXSESSION = 8
DEFAULTMINCOWINNER = 4
DEFAULTMINCOLOSER = 4
MAXAUTOACT = 0
RCVWINDOW = 3
SENDWINDOW = 3
DEFAULTMAXINRUSIZE = process’ MAXINRUSIZE
DEFAULTMAXOUTRUSIZE = process’ MAXOUTRUSIZE
•
#BATCH PTNR-MODE
$<apc-process>.<local-LU>.<partner-LU>.“#BATCH” is the object name of the
#BATCH PTNR-MODE in a SNAX/APC subsystem. It could be used by any