SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
4-6
Static and Dynamic Configuration
Hierarchies are useful for wild-card referencing; for example in SNAX/APC there may
be multiple instances of a transaction program (the TPN object type) running
simultaneously. In such a case, an object specification of the form TPN * can be used
to refer to all current instances of the TPN. Similarly, as the full example at the end of
this section shows, all LUs can be started with a START LU * command. Refer to
Part II, SCF Reference for SNAX/APC
for further information on the use of wild-card
characters.
Static and Dynamic Configuration
The convention for type LU6.2 configurations is that you have to define all the remote
LUs (and modes) that you expect to have conversations with — before a session request
is received. In other words you must decide ahead of time the applications and LUs that
you may contact or who may contact you. This is a static definition. It takes time and
effort to configure the system, and the static definition does not allow you to provide
service to remote LUs who wish to make unsolicited contact with your local LU. If you
are operating a local LU as part of a server system, you may not know ahead of time
which clients may want to contact you.
Tandem’s implementation of type LU6.2 also allows a dynamic configuration. There are
three levels of support for dynamic configuration:
1. SNA-defined mode names — simple support for parallel sessions.
You configure the remote LU only (as a parallel-session LU), and allow SNAX/APC
to create all the modes to be associated with that remote LU. This merely saves you
the effort of configuring all possible PTNR-MODE objects. These mode names are
defined in the SNA architecture and are widely implemented in type LU6.2 system
products that may establish sessions with Tandem systems. See Configuring a Mode
on page 4-19 for further details.
2. Dynamic PTNR-LU support — for unsolicited BINDS from unknown remote LUs.
You do not configure the remote LU or its modes, but you open a line to an access
method such as SNAX/XF, SNAX/CDF, or SNAX/APN (using the
SNAXFILENAME attribute). You must also configure the local LU (associated
with that line) with DYNAMICSUPPORT YES, and you should configure it for
either single or parallel session support. After the subsystem is started, and upon
receipt of an unsolicited BIND received on that line, the SNAX/APC subsystem will
read the BIND, determine if it is a single or parallel session request and then create
the appropriate PTNR-LU and PTNR-MODE objects to allow a session between the
local LU and the remote LU. SNAX/APC will start these dynamic objects and will
also delete them when the session is terminated. See Configuring a Local LU
on
page 4-11 and Configuring a Partner LU
on page 4-26 for further details.
3. Dynamic SNAXFILENAME support —using SNAX Creator-2 for unsolicited
BINDs from unknown remote LUs.
You do not configure the remote LU or its modes and you do not open a line to an
access method (by leaving the SNAXFILENAME attribute blank), instead you
configure the SNAX Creator 2 to forward BINDs (received on any line) to the