SNAX/APC Management Programming Manual

ADD PTNR-MODE
Commands and Responses
111813 Tandem Computers Incorporated 5–21
The PTNR-MODE object named SNASVCMG has the following default attribute
settings:
ZAPC-TKN-MODE-NAME = SNASVCMG
ZAPC-TKN-D-SESS-LIM = 2
ZAPC-TKN-D-MAXINRUSIZE = MAXINRUSIZE value from process startup
or 256
ZAPC-TKN-D-MAXOUTRUSIZE = MAXOUTRUSIZE value from process
startup or 256
ZAPC-TKN-D-MIN-CONWINNERS-LIM = 1
ZAPC-D-MIN-CONLOSERS-LIM = 1
ZAPC-TKN-AUTO-ACTIVATE-LIM = 1
ZAPC-TKN-RCV-PACING-WINDOW = 7
ZAPC-TKN-SEND-PACING-WINDOW = 7
The only token values that can be altered are ZAPC-TKN-AUTO-ACTIVATE-LIM,
ZAPC-TKN-RCV-PACING-WINDOW, and ZAPC-TKN-SEND-PACING-
WINDOW.
The remainder of the token values are architected as described in the IBM Systems
Network Architecture Format and Protocol Reference Manual.
Maximum RU (request unit) size is limited by the underlying access method.
SNAX/XF and SNAX/CDF support RUs up to 4,096 bytes. SNAX/APN supports
RUs up to 16,000 bytes.
Since SNAX/APC is unable to find the upper limit of the underlying SNAX access
method (such as SNAX/APN, SNAX/XF, or SNAX/CDF) of an LU until the LU is
started, the ZAPC-TKN-D-MAXINRUSIZE and ZAPC-TKN-D-MAXOUTRUSIZE
tokens are not validated against the underlying SNAX access method. However if
the values of these tokens exceeds the upper limit of the underlying SNAX access
method, the ZAPC-TKN-CUR-MAXINRUSIZE and ZAPC-TKN-CUR-
MAXOUTRUSIZE tokens (in the INFO PTNR-MODE response buffer) are set to
the upper limit after the PTNR-MODE is started. If the values of the ZAPC-TKN-
D-MAXINRUSIZE and ZAPC-TKN-D-MAXOUTRUSIZE tokens do not exceed the
upper limit, the ZAPC-TKN-CUR-MAXINRUSIZE and ZAPC-TKN-CUR-
MAXOUTRUSIZE tokens are set when the PTNR-MODE object is started to the
values specified in the ZAPC-TKN-D-MAXINRUSIZE and ZAPC-TKN-D-
MAXOUTRUSIZE tokens.