SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC
SNAX/APC Configuration and Management Manual138787
4-11
Configuring a Local LU
that support SNALUXS, which is the SNAX/APN interface used in this mode of
operation. There is a slight difference in the mechanics of SNAX/APC and SNAX/HLS.
SNAX/APC is the direct target of the SNAX Creator-2 with regard to passing the
bindimage and openname. With the SNAX/HLS model, the SNAX Creator-2 will
actually open and pass the openname to the application program that uses SNAX/HLS
(Pathway) and that program will open SNAX/HLS. This means that the configuration of
SNAX Creator-2 will be different.
For further details on SNAX/HLS consult the SNAX/HLS Configuration and Control
Manual.
Configuring a Local LU
The local LU is the one that resides on the Tandem system—although it need not be on
the same Tandem node as the SNAX/APC process. It is the LU through which the local
transaction programs gain access to the SNA network.
To configure a local LU, the minimum specification requirements are:
Local name (LU object name) and SNA network name of the LU (SNANAME
attribute)
Tandem access method to be used (SNAXFILENAME attribute). If you do not
specify an access method, but just type SNAXFILENAME without a process name
it is assumed that you are requesting dynamic SNAXFILENAME support.
When the minimum requirements are specified, you also get the following defaults:
AUTOSTART NO, MAXSESSION 1 (single-session LU), DYNAMICSUPPORT NO,
SNAXMAXRETRYCOUNT 0 (no retries) and LOCAL-LU-SYNC2-SUPPORT NONE.
Optionally, you can define the following characteristics:
Number of sessions (single or parallel) with MAXSESSION attribute
Autostart capability with AUTOSTART attribute
The number of retries of the open to the underlying access method after an error
occurs (specified with the SNAXMAXRETRYCOUNT attribute)
The amount of time between each attempt to reopen the underlying SNAX access
method after an error occurs (specified with the SNAXRETRYTIMER attribute)