SNAX/HLS Management Programming Manual

4 Elements of SPI Messages for
SNAX/HLS
104708 Tandem Computers Incorporated 4–1
This section describes the portions of Subsystem Programmatic Interface (SPI)
messages that have specific meaning to SNAX/HLS.
SNAX/HLS Definition
Files
The tokens and other definitions for SNAX/HLS are provided by the following six
definition files:
ZSPIDEF. ZHLSCOB contains COBOL85 definitions.
ZSPIDEF. ZHLSDDL contains DDL definitions.
ZSPIDEF. ZHLSTACL contains TACL definitions.
ZSPIDEF. ZHLSTAL contains TAL definitions.
ZSPIDEF. ZHLSC contains C definitions.
ZSPISEGF. ZHLSSEGF contains TACL segment form of ZHLSTACL file.
You should also include the ZSPI, ZCOM, and ZCMK files contained in the ZSPIDEF
subvolume. If you want your program to monitor events or control the EMS
subsystem, you must also include ZEMS definitions.
In addition, some events and responses generated by SNAX/HLS contain data defined
by the file system (ZFIL) and the Tandem NonStop Kernel routines (ZGRD).
Naming Rules and
Guidelines for
Applications
By convention, Tandem uses names beginning with the letter Z for all definitions and
all component fields of structures in its definition files. To avoid conflicts with names
defined by Tandem, do not begin any names that you define in your applications with
uppercase or lowercase Z.
Objects This section discusses object types, object hierarchy, object names, object referencing,
and object summary states.
Object Types The control–and–inquiry interface to SNAX/HLS deals with the SNAX/HLS process
itself and the sessions managed by the process. The object types that can be used in
the interface are:
PROCESS Object Type
The PROCESS object type, ZCOM–OBJ–PROCESS, is used when the object of a control
or inquiry operation is the SNAX/HLS process itself. Because such a command is
directed to the instance of the SNAX/HLS process handling the request, no object
name is required for a PROCESS object. The name of the SNAX/HLS process is
accepted, if present.
SESSION Object Type
The SESSION object type, ZCOM–OBJ–SESSION, is used when the object of a control
or inquiry operation is a session known to the specific instance of SNAX/HLS to
which the command is addressed. SNAX/HLS reserves no specific names for session
objects.