SNAX/HLS Configuration and Control Manual

Step 4. Planning the Application Environment
Planning the SNAX/HLS Environment
2–20 104705 Tandem Computers Incorporated
MAXLINKS. This parameter is a global server parameter that directly affects
SNAX/HLS performance. MAXLINKS is the number of file opens of SNAX/HLS that
the TCP is allowed. Be sure that the MAX^POCB of the SNAX/HLS server is great
enough to handle MAXLINKS plus HLSCOM requirements. The calculation below
gives the exact link demand of a SNAX/HLS process. You can let MAXLINKS default
to unlimited.
Calculate this parameter as follows:
For each TCP, define the link demand as:
LD(i) = (SL(i)+14)/15
Calculate MAXLINKS as the sum of all LDs plus one (for HLSCOM).
MAXSERVERS. This must be the value 1.
NUMSTATIC. This must be the value 1.
OUT. Specify the log file for the SNAX/HLS server process here. See Section 4,
“Building the Resource Definition Table” for more information on the log file.
PARAM. In Pathway environments before release B30, the PARAM facility cannot be
used to communicate with the SNAX/HLS server; you must use the STARTUP
method described below.
PROCESS. Specify the SNAX/HLS server-process name here. This name is mandatory
because it appears as the first component of the LU name. Do not specify a network
file name here. If the SNAX/HLS server process is remote, use the PROGRAM
statement to specify the network node name.
PROGRAM. Specify the disk location of the HLSOBJ file in this parameter. If a network
file is specified, the SNAX/HLS process is considered remote.
STARTUP. Specify any startup message parameters here, such as DEBUGONERROR or
MAX^POCB.
VOLUME. Specify the default volume to be delivered in the startup message here. The
default volume defines where the extended data segments are swapped, unless
overridden by the SWAPVOL parameter.
Selecting PROFILE
Attributes
The PROFILE attributes allow control of the interface between the application and
SNAX/HLS. Of particular interest here are those attributes that restrict the types of
information that can flow from SNAX/HLS to the application. In most cases, these
attributes are specified by the PROFILE, although in some cases, the issuance of certain
SNAX/HLS requests affects the messages that can be delivered to the application.
SSCP Text
The PROFILE attribute, WANT-SSCP-TEXT, is used to control whether text received
from the SSCP is to be delivered to your application. The messages affected are
character-coded messages from the SSCP. It is unlikely that this attribute should be
selected.