SNAX/HLS Configuration and Control Manual

Using HLSRUN to Configure PATHWAY
Installing SNAX/HLS
104705 Tandem Computers Incorporated 3–11
TRACE trace-option
designates the setting for the INITIAL^TRACE option used at SNAX/HLS
startup. If omitted, the value zero is assumed. (For more information on
INITIAL^TRACE, refer to Section 5, “Operating SNAX/HLS.”)
TCLPROG pathway-program-file-name
designates where the object of the Pathway SCOBOL program file and the
corresponding directory is located. The file name portion cannot exceed five
characters. If omitted, HLSP on the HLS subvolume is assumed. If specified,
the files are located using the current #PMSEARCHLIST.
Pathway-program-file-name designates where the PATHWAY program
file is located. The file-name portion cannot exceed five characters.
System programmers should review the HLSRUN file for details on required
parameters for Pathway installation. In particular, programmers should review the
description of the SNAX/HLS process as a server class prior to the installation of
SNAX/HLS into any other Pathway system. Consideration should be given to:
Pathway owner and security. This controls which IDs are allowed to alter the
operational state of the Pathway system.
Program owner and security. Set the security to local standards. Remember that
all application programmers probably need access to APS.
Current #PMSEARCHLIST. The TACL built-in variable #PMSEARCHLIST defines
the subvolumes that are searched and the order in which the search occurs. It is
critical that the particular version of the HLSOBJ file that you wish to run be
located on one of the subvolumes encountered. Normally, the following TACL
statement ensures that TACL will locate the HLSOBJ file:
#SET #PMSEARCHLIST #DEFAULTS $SYSTEM.SYSTEM
This statement directs TACL to search the current subvolume and then
SYSTEM.SYSTEM. If you define your current subvolume to the site of the HLSOBJ
file, the HLSRUN macro will work properly.
The HLSOBJ file owner and security. Normally, the files HLSOBJ and HUXOBJ
are executable by a wide community of users. However, if you are the first to
execute the HLSOBJ file since the file was installed or moved, the Tandem
NonStop Kernel must update the library references. This operation requires write
access to the HLSOBJ file.