SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
4-28
Configuring a Partner LU
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 rest of the SNA-defined PTNR-MODEs will be brought up through
subsequent CNOS operations.
These dynamic objects will be brought down to the STOPPED state and removed from
the local LU’s configuration after all of the subordinate sessions are terminated.
The ADD PTNR-LU Command
The ADD PTNR-LU command defines a partner LU to a local LU. The attribute
specification for the PTNR-LU object of the SNAX/APC ADD command consists of the
following attribute name and value combinations:
PTNR-LU partner-lu
identifies the name of the partner LU.
LIKE partner-lu2
identifies an existing partner LU whose attribute values serve as the model for the
values of the attributes of the partner LU being created.
SNANAME uninterpreted-lu-name
specifies the name of the partner LU as it is known in the SNA network. It can be
up to 17 characters long if it is entered in the form:
[net-id.]partner-LU-name
where net-id is up to 8 characters long and partner-LU-name is up to 8
characters long.
The net-id name value is the name of the SNA network in which the partner LU
resides.
Note that the object name entered for partner-LU-name is the name by which
the partner LU is known to the Tandem system. The SNANAME, rather than the
partner LU object name, is used for building SNA requests (such as BIND).
ADD [ PTNR-LU partner-lu1 ] [ , LIKE partner-lu2 ] , attr-
spec
where attr-spec is:
, SNANAME uninterpreted-lu-name
[ , LOCAL-LU-SECURITY-ACCEPTANCE { NONE | CONV |
ALREADYVERIFIED } ]
[ , PARALLEL-SESSION-LU { YES | NO } ]
[ , PERIPHERAL-NODE { YES | NO } ]