SNAX/HLS Configuration and Control Manual

Step 4. Planning the Application Environment
Planning the SNAX/HLS Environment
104705 Tandem Computers Incorporated 2–19
SET TERMINAL Parameters
The SET TERMINAL parameters should be specified as follows.
FILE. (For SNAX/XF) Provided that your application extracts server class and LU
names as outlined above, you use this parameter to convey the identity of the session
partner by providing an entry of the form:
$ HLS-process-name .# SNAX/XF-line-name . LU-name
(For SNAX/CDF) Use this parameter to convey the identity of the session partner by
providing an entry of the form:
$HLS-process-name.# CDF-process-name.openname-of-appl
Using this method to communicate the names excludes the use of the terminal for
operator communication.
SET SERVER Parameters
The SET SERVER parameters should be specified as follows.
HOMETERM. The home terminal for the SNAX/HLS server can be set with this
command.
IN. Name the RDT object for SNAX/HLS initialization in this parameter. See Section 4,
“Building the Resource Definition Table” for more information.
LINKDEPTH. This parameter is a global server parameter that affects SNAX/HLS server
performance. LINKDEPTH is the number of outstanding I/Os to the SNAX/HLS
server that the TCP issues before internally queuing further requests. LINKDEPTH
interacts with MAXLINKS in the sense that the TCP issues no more than 15 I/Os on
any one link at any one time. Thus, you must configure LINKDEPTH to allow for one
verb from each requester to be outstanding. If the calculation given below yields a
value greater that 255, the TCP internally queues verbs, and you should consider
adding more SNAX/HLS server classes.
Calculate this parameter as follows:
For each TCP sending SNAX/HLS verbs to this server class, define the session
limit of the TCP as:
SL(i) = total number of SNAX/HLS requesters supported by TCP TCP(i).
Calculate LINKDEPTH as the sum of all SLs.