SNAX/HLS Configuration and Control Manual

Step 4. Planning the Application Environment
Planning the SNAX/HLS Environment
2–18 104705 Tandem Computers Incorporated
MAXTERMDATA. The only SCOBOLX requester delivered with SNAX/HLS is the APS
system. The information required to set this value can always be obtained from a
SCUP INFO DETAIL command on the HLSP program libraries. A value of 23,000 is
suggested for APS.
PROGRAM. The standard Pathway configurations delivered with SNAX/HLS always
specify PATHTCP2. Remember that SNAX/HLS must run on a NonStop system (and
cannot run on a NonStop 1+ system). In general, it is assumed that the Pathway
systems communicating with SNAX/HLS reside on the same systems as SNAX/HLS.
This is not a requirement, however. A Pathway TCP running on a NonStop system or
a NonStop 1+ system can access a SNAX/HLS server class on a network-accessible
NonStop system. If the Pathway system resides on a NonStop 1+ node, use PATHTCP
for this entry.
TCLPROG. Either the TCP or the PROGRAM statements for the APS system must
specify HLSP for the SCOBOLX libraries.
SET PROGRAM Parameters
The SET PROGRAM parameters should be specified as follows.
PRINTER. The APS system can print screens. Printers should be defined according to
local standards.
The suggested default parameter is a spooler file, such as $S.#APS.
OWNER/SECURITY. Set the fields on these parameters in accordance with installation
policy on APS access.
TYPE. The only requester delivered with the SNAX/HLS system, APS, uses only those
functions available on T16-6520 terminals. The INITIAL program run unit is APS for
the APS system.