OSI/MHS Management Programming Manual

Common Definitions
OSI/MHS Management Programming Manual—424824-001
4-17
Standard Subsystem Programmatic Interface
(SPI) Tokens
ZMHS-TKN-LOOP-DETECTED (ZSPI-TYP-BOOLEAN)
contains a token indicating whether crash-looping has been detected when an
internal error event is generated. The possible values are:
ZMHS-TKN-CUG-VIOL-RSN (ZSPI-TYP-ENUM)
contains a token indicating the reason for the CUG violation. The possible values
are:
ZMHS-TKN-CONTENT-TYPE (ZSPI-TYP-STRING)
is a string containing the content type value; maximum length is 32 bytes. For
builtIn content types, it is a single integer value, for example, 1. For external
content types, the string is a sequence of integers separated by commas, for
example, 2,6,3,3,0.
Standard Subsystem Programmatic Interface (SPI) Tokens
This subsection describes the SPI tokens that might be included in OSI/MHS specific
event messages. Refer to the individual event description in Section 6, Event Messages,
to determine if one of these tokens is considered a core token for that event.
ZSPI-TKN-SSID
identifies the subsystem ID. This token appears in all events.
ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST
define an error list included in an event buffer.
ZSPI-TKN-ERROR
identifies an error and its owner.
ZSPI-TKN-MANAGER
identifies the name of the manager process of the OSI/MHS subsystem in which the
error occurred.
ZSPI-VAL- Value Meaning
TRUE -1 Loop detected, PDU marked as inactive
FALSE 0 Loop not detected
ZMHS-VAL-CUG-VIOL-RSN- Value Meaning
ORIG 0 Originator not in any CUG
RESTRICT 1 Failed CUG restrictions for all CUGs
containing originator
RECIPS 2 Recipient(s) have no CUG in common with
originator