OSI/AS Management Programming Manual

INFO ENTRY Command
Commands and Responses
5–116 056785 Tandem Computers Incorporated
ZCOM-TKN-CMD-TIMEOUT
is described in the Communications Management Programming Manual.
ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT,
and ZSPI-TKN-CONTEXT
are described in the Distributed Systems Management (DSM) Programming Manual.
Tokens in Response Buffer
ZSPI-TKN-DATALIST
introduces a data list, as described in the Distributed Systems Management (DSM)
Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list. These
tokens enclose the other response tokens only if the value of the header token
ZSPI-TKN-MAXRESP is nonzero.
ZCOM-TKN-OBJTYPE and ZCOM-TKN-OBJNAME
are described in the Communications Management Programming Manual.
For each ENTRY identified by a ZCOM-TKN-OBJNAME token, the response
includes one of the following tokens:
ZOSI-MAP-INFO-ENTRY-APPL for an application ENTRY
ZOSI-MAP-INFO-ENTRY-NSAP for an NSAP ENTRY
ZOSI-MAP-INFO-ENTRY-SNPA for an SNPA ENTRY
ZOSI-MAP-INFO-ENTRY-TSEL for a TSEL ENTRY
ZOSI-MAP-INFO-ENTRY-APPL
is an extensible structured token that contains the current attributes of the
specified application ENTRY in the MIB. ZOSI-DDL-INFO-ENTRY-APPL
contains the following fields:
ZSERV-LEV
is reserved for Tandem internal use and should not be used by your
application.
ZNSAP-LEN
is the length of the NSAP address specified in ZNSAP. The range of values is 0
through 20 bytes. For example, if your NSAP address is “ABC,” the ZNSAP
value is a two byte field “ABC0,” (it’s internally padded with a 0 to make an
even number of digits). ZNSAP-LEN field would be “2.” See the ZNSAP-
NIBBLE field for related information regarding the use of odd length NSAPs.