SNAX/HLS Management Programming Manual

Objects
Elements of SPI Messages for SNAX/HLS
104708 Tandem Computers Incorporated 4–3
If the session was established using a SNAX/CDF APPL to gain access to the SNA
network, the qualifiers are a converted form of the OPENNAME of the APPL. For
example, if the SNAX/CDF process is $CDF and the OPENNAME of the APPL is
#APPL1 then the session name on a stand-alone Tandem system would be:
$HLS.#CDF.APPL1
Note that for SNAX/XF the LU name, LUX in the above example, and for SNAX/CDF
the APPL name, APPL1 in the above example, is limited to seven characters.
Objects Referencing There are three methods that a requester can use to indicate to which objects a given
command is to be applied:
Object–name templates
The SUB modifier
The SEL–SUMSTATE modifier
These three methods can be used simultaneously. It is the responsibility of the
requester to make sure that the referenced objects make sense for the command. For
example, an attempt to issue an ALTER PROCESS command produces errors if the
SUB modifier causes the command to be applied to sessions.
Uppercase and lowercase letters can be used interchangeably when referencing
objects. Note, however, that object names generated by SNAX/HLS in responses or
event messages are all uppercase.
Object–Name Templates
SNAX/HLS supports object–name templates that include an asterisk (*) for any
nonblank characters and a question mark (?) for a single nonblank character. The use
of asterisks and question marks (wild–card characters) is limited to the LU portion of
object names only; they cannot be used in the process name.
In its simplest form, a template contains no wild–card characters. Such a template
identifies at most one session and has one of the forms shown below, dependent on
the Tandem SNA access method is being used. The two Tandem SNA access methods
SNAX/HLS can use currently are SNAX/XF and SNAX/CDF.