SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
4-15
Configuring a Local TP Name
Examples
The following is an example of configuring a local LU:
-> ADD LU $APC1.LLU01, SNANAME TNDLU01, SNAXFILENAME &
$nt21A.#LU101, MAXSESSION 255, AUTOSTART YES, &
SNAXMAXRETRYCOUNT 20, SNAXRETRYTIMER 30000
The following shows the same example, using dynamic and sync point support:
ADD LU $APC1.LLU01,SNANAME TNDLU01,SNAXFILENAME , &
MAXSESSION 255, AUTOSTART YES, SNAXMAXRETRYCOUNT 20, &
SNAXRETRYTIMER 30000, DYNAMICSUPPORT YES, &
LOCAL-LU-SYNC2-SUPPORT SYNCPT
Configuring a Local TP Name
The local TP is 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 local transaction program (the
TP based on the Tandem system) that requires access to the SNA network for
conversations with partner programs elsewhere in the SNA network.
To configure a local TP, the minimum specification requirements are:
•
The name of the TP object.
When the minimum requirements are specified, you also get the following defaults:
CHARMAPPING NO, GENERALTPREADY NO, REMOTEATTACH QUEUE,
REMOTEATTACHTIMER -1 (timer will wait indefinitely),
REPLYDELAYEDONERROR NO, SECURITYREQUIRED NONE, and
SESSIONCONTROL NO.
Optionally, you can define the following characteristics:
•
Support of the general TP-READY feature (GENERALTPREADY attribute). A TP
that waits for a remote TP to start a conversation can either wait for a conversation
request on a specific local LU (a specific TP-READY) or wait for a conversation
request on any local LU (a general TP-READY).
•
Session control capabilities (SESSIONCONTROL attribute). In general, session
control is the province of the network controller rather than the individual user
(program).
•
Queuing of remote ATTACH requests (REMOTEATTACH and
REMOTEATTACHTIMER attributes).
•
When to a reply to a waiting TPREADY verb after an error
(REPLYDELAYEDONERROR)
•
Character translation for all mapped conversations subordinate to the TPN can be
specified (CHARMAPPING attribute) along with the translation table to be used for
the character translation (CHARMAPNAME attribute).
•
Whether or not security tests will be performed before granting access to server TPs
(SECURITYREQUIRED attribute).