SNAX/APC Configuration and Management Manual

Using SNAX/APC
SNAX/APC Configuration and Management Manual—138787
3-16
Using APCRUN to Set Up the PATHMON
Environment
MODE objects may specify different values. If a MAXINRUSIZE value is not
specified for an individual PTNR-MODE object, it gets this value.
If SNAX/APC is the primary LU, it sends this value in the BIND request.
If SNAX/APC is the secondary LU, its BIND response returns the lesser of
MAXINRUSIZE and the BIND RU size. If the BIND RU size is less than 16,
SNAX/APC returns 16.
MAXO[UTRUSIZE] number
specifies the maximum number of bytes in the outgoing SNA Request/
Response Unit (RU) to the Tandem access method (the BIND RU size).
Allowable values are in the range 16 through 16,000; 256 is the default value.
This specifies the default value for the SNAX/APC process. Individual PTNR-
MODE objects may specify different values. If a MAXOUTRUSIZE value is
not specified for an individual PTNR-MODE object, it gets this value.
If SNAX/APC is the primary LU, it sends this value in the BIND request.
If SNAX/APC is the secondary LU, its BIND response returns the lesser of
MAXOUTRUSIZE and the BIND RU size. If the BIND RU size is less than 16,
SNAX/APC returns 16.
The relation between the value of MAXOUTRUSIZE and the PU RECSIZE
(which is specified in the SCF configuration for the underlying access method)
controls whether or not SNAX/APC will send segmented RUs to the remote LU.
SNAX/APC will send segmented RUs if MAXOUTRUSIZE + FID2 TH
(Transmission Header—6 bytes for FID2 TH) is greater than the PU RECSIZE.
If the remote LU does not support segmentation, you must ensure that
MAXOUTRUSIZE + TH is less than the PU RECSIZE. SNAX/APC will send
segmented RUs even if the remote LU specifies in the BIND (or BIND
response) that it does not support segmented RUs.
NODISPLAY[PARM]
suppresses the display of APCRUN settings when APCRUN is run. If you omit
this parameter, APCRUN displays a list of its options and their current values
when it is run.
NOL[OG]
If present, SNAX/APC server processes will not generate log messages to a log
file. If not present the log file for the servers will default to ZxxnnLG (See
Names Created by APCRUN) below. We recommend that you do not create a
separate file log file for SNAX/APC messages—use the EMS collectors instead.
PATHC[OM] subvolume
specifies the subvolume on which the PATHCOM program file resides. If this
option is omitted, the list of subvolumes specified by the TACL built-in
#PMSEARCHLIST is used.