SNAX/APC Configuration and Management Manual

SCF Commands for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
8-56
INFO PTNR-LU Command
system. The SNANAME, rather than the partner-lu name, is used for building
SNA requests (such as the session activation BIND request).
Peripheral Node
YES indicates that the partner LU resides on a peripheral node. It also implies that
the partner LU is a secondary LU (SLU) if the PARALLEL-SESSION-LU attribute
is set to NO.
NO indicates that the partner LU resides on a subarea node. It also implies that the
partner LU is a primary LU (PLU) if the PARALLEL-SESSION-LU attribute is set
to NO.
If the local LU is a parallel-session LU, or its underlying access method is a type 2.1
node LU, this indicator does not imply the partner LU’s role (SLU or PLU).
Parallel Sess-LU
displays whether or not the partner LU supports parallel sessions. YES indicates
that the partner LU is a parallel-session LU (or supports parallel sessions). NO
indicates that the partner LU is a single-session LU; therefore the local LU will not
initiate or expect any CNOS commands.
INFO PTNR-LU Detailed Display
This example shows the request for detailed information about the partner LU named
CICS:
-> INFO PTNR-LU $APC1.LU01.CICS
The following display is returned in response to this request:
SNAName
is the name of the partner LU as it is known in the SNA network. Note that the
object name partner-lu is the name by which the LU is known to the Tandem
system. The SNANAME, rather than the partner-lu name, is used for building
SNA requests (such as the session activation BIND request).
SNAX/APC DETAILED INFO PTNR-LU: $APC1.LU01.CICS
*SNAName ................................. CICS
*PERIPHERAL-NODE ......................... NO
*PARALLEL-SESSION-LU ..................... YES
LOCAL-LU-SECURITY-ACCEPTANCE ............ USER
REMOTE-LU-SECURITY-ACCEPTANCE ........... ALREADYVERIFIED
Note. Attributes marked with an asterisk (*) can be altered using the ALTER command.