SNAX/HLS Configuration and Control Manual

Program Security
Installing SNAX/HLS
104705 Tandem Computers Incorporated 3–5
HLSTAP Trace Analysis The trace analysis program (HLSTAP) can also be placed on $SYSTEM.SYSTEM for
ease of use, although this depends on the frequency of trace analysis.
HUXOBJ Library File It is recommended that HUXOBJ be put on $SYSTEM.SYSTEM since the library
location of HLSOBJ, by default, is $SYSTEM.SYSTEM.HUXOBJ.
ZHLSTMPL Template File Your installation should use the Install process to install the messages for SNAX/HLS
into the system’s template file. Then this file does not have to be accessible.
Other Files Other files can be moved to achieve optimal tuning. Because SNAX/HLS is not often
installed, the HLSOBJ file and the HLSRDT object file need not be put in
$SYSTEM.SYSTEM.
HLSMSGS Message File HLSMSGS (the message file) must be put in a subvolume where it is accessible to the
programs that use it (the HLSOBJ files, the HLSRDT program, the HLSCOM program,
and the HLSTAP program). Assuming the HLSOBJ file is put in
$PROGS.HPROG.HLSOBJ and HLSTAP is also put in $PROGS.HPROG.HLSTAP, the
message file can be put in any of the following three files:
$PROGS.HPROG.HLSMSGS
$PROGS.SYSTEM.HLSMSGS
$SYSTEM.SYSTEM.HLSMSGS
The HLSOBJ file and the HLSRDT, HLSCOM, and HLSTAP programs search for the
message file in the following order:
1. Search for HLSMSGS in the volume and subvolume containing the program.
2. Search for HLSMSGS in the subvolume named SYSTEM on the volume containing
the program.
3. Search for HLSMSGS in $SYSTEM.SYSTEM.
Program Security The process owner of the HLSOBJ file can use the STOP command of a command
interpreter, or the ABEND command of HLSCOM to stop the SNAX/HLS process for
internal problem determination. A member of the SNAX/HLS process owner’s group
ID can ABORT LUs under the SNAX/HLS server control. See Section 6, “Using
HLSCOM” for information on the control of the SNAX/HLS process. The following
paragraphs contain recommendations for setting SNAX/HLS security.
HLSOBJ Security Secure the HLSOBJ file as owned by the manager of a special group or by a member of
the SUPER group. Consider turning on the PROGID attribute for the HLSOBJ file.
The installation can carefully control the abending of the SNAX/HLS process with
PROGID set to a specific owner. SUPER.SUPER can always abend a SNAX/HLS
process.
HLSMSGS and ZHLSTMPL
Security
Secure these files to be readable by anybody. This allows all instances of the HLSOBJ
file and the HLSTAP, HLSCOM, and HLSRDT programs to access message texts.