SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
4-10
Configuring a Server Mechanism
Step Five:
Upon receipt of this message, the SNAX/APC process first validates the local LU names
and responds positively to the Creator-2 process (or rejects the message if the SLU
(Local LU) name could not be found).
Secondly, the SNAX/APC process adds the dynamic PTNR-LU object and a list of
SNA-defined PTNR-MODE objects. The process is slightly different for single and
parallel session LUs.
For a single-session LU:
•
A PTNR-LU object is automatically added to the local LU with the specified PLU
name.
•
A PTNR-MODE object is also added to the PTNR-LU object with the specified
MODE name.
•
SNAX/APC will start the PTNR-LU and PTNR-MODE objects.
•
The local LU uses the given line handler’s open name to retrieve the incoming
unsolicited BIND request, and continues the session initiation.
•
These dynamic PTNR-LU and PTNR-MODE objects will be placed in STOPPED
state and removed from the local LU after the session is deactivated.
For a parallel-session LU:
•
The BIND request will be rejected if the MODE name is not SNASVCMG.
•
A PTNR-LU object is automatically added to the local LU with the specified PLU
name.
•
SNAX/APC will add default PTNR-MODE objects for all of the SNA-defined mode
names.
•
SNAX/APC will start the PTNR-LU and the SNASVCMG PTNR-MODE objects
•
The local LU uses the given line handler’s open name to retrieve the BIND request,
and then continue the session initiation.
•
SNAX/APC will exchange CNOS requests with the remote LU.
•
SNAX/APC will perform more session initiations for SNA-defined mode names.
•
The dynamic PTNR-LU and PTNR-MODE objects will be placed in STOPPED
state and removed after all of the sessions are deactivated.
Because the SNAXFILENAME is dynamically defined, no session could be initiated
locally before a BIND is received from the partner LU. An attempt to initiate a local-
attached TP-READY (a TP-READY with the local -attach-indicator set to Y) will
receive a file system error 14 indicating an unknown device. However, a remote-
attached TP-READY (a TP-READY with the local -attach-indicator set to N) will be
queued and processed when a BIND is received from the partner LU.
It should be noted that the same form of sever mechanism can be created use in
SNAX/HLS as well as SNAX/APC. These high-level APIs are the only applications