SNAX/HLS Management Programming Manual

Objects
Elements of SPI Messages for SNAX/HLS
4–2 104708 Tandem Computers Incorporated
NULL Object Type
The NULL object type, ZCOM–OBJ–NULL, is used only in the GETVERSION and
LISTOBJECTS commands, where it has a special meaning. The NULL object type has
no other use in SNAX/HLS.
Object Hierarchy Sessions are considered subordinate to the SNAX/HLS process. No other hierarchy is
assumed by SNAX/HLS.
Object Names All object names generated by the SNAX/HLS process consist of uppercase characters.
The NULL object has no object name; the object name must be of zero length or
omitted.
The PROCESS object name is the name of the SNAX/HLS process. Either of the
following notations is used:
\node.$process
or
$process
The SNAX/HLS process name generated by the subsystem is always the fully
qualified network name (if the node is within a network). As a result, some process
names (those of five characters) might not be translatable to internal notation.
The object name of a SESSION object consists of the name of the SNAX/HLS process
as outlined above, followed by SESSION qualifiers. The SESSION object name is one
of the following depending on whether or not the Tandem system is a node in a
network:
\node.$process. qualifiers
or
$process. qualifiers
The form of the session qualifiers are dependent upon the Tandem SNA access
method. For example, SNAX/XF is used by SNAX/HLS to gain access to the SNA
network. The session qualifiers name a specific LU the same way qualifiers are used
by the LU-name field of the SNAX/HLS OPEN–SESSION or HLS–ALLOCATE verb.
If the session is using a SNAX/XF LU then the qualifiers are the converted LU name.
For example, if the SNAX/XF LU is $SNA.#LUX and the SNAX/HLS process is $HLS,
then the session name on a stand-alone Tandem system would be:
$HLS.#SNA.LUX