SNAX/HLS Configuration and Control Manual

5 Operating SNAX/HLS
104705 Tandem Computers Incorporated 5–1
Starting SNAX/HLS Once SNAX/HLS is installed (as described in Section 3, “Installing SNAX/HLS”) and
the appropriate Resource Definition Table (RDT) is compiled, you can start the
SNAX/HLS process using the RUN HLSOBJ command described in the next
subsection.
When the SNAX/HLS server is started, the version banner is sent to the log file (if
logging is enabled) and an EMS event is generated. A command operator or system
programmer can execute the HLSCOM PEEK command to verify startup parameters.
Consideration at this step should be given to the following:
The number of SNAX/HLS processes. You can collect performance statistics
using system services XRAY or MEASURE utilities and the HLSCOM PEEK
command. Consult your Tandem analyst for assistance in this area.
Log-file assignment. The SNAX/HLS process accesses the log file in a wait
fashion. Refer to “The LOG Facility” later in this section for more information.
Home-terminal assignment. If the SNAX/HLS process terminates abnormally, or
if an internal error is detected and the startup parameter DEBUGONERROR is set
to OFF, the SNAX/HLS server calls the procedure ABEND. If the SAVEABEND
feature is enabled (with INSPECT SAVEABEND), a SAVEABEND file is created
with a name in the form:
$ default . default .ZZSA nnnn
where nnnn is a unique four-digit number and the volume and subvolume are the
process defaults of the SNAX/HLS process at creation. The location of the
SAVEABEND file is displayed on the home terminal. HLS control operators
should be able to view or retrieve the name of the SAVEABEND file.
Startup-parameter assignment. SNAX/HLS is fully configurable at startup. Either
configuration parameters or command interpreter PARAM statements can be used
to configure the operational environment of the SNAX/HLS process.