OSI/MHS Management Programming Manual

Event Messages

OSI/MHS Management Programming Manual—424824-001

6-72

14: ZMHS-EVT-SPI-BAD-OCCURS

An SPI message was received with a byte count that cannot occur in a well-formed

request message. This is not a critical event.

Token Descriptions

ZMHS-TKN-XPNAME

is the name of the process involved in the event; maximum length is 128 bytes.

ZEMS-TKN-EMPHASIS

has the value ZSPI-VAL-FALSE, indicating that this is not a critical event.

ZEMS-TKN-CONSOLE-PRINT

has the value ZSPI-VAL-TRUE.

Cause. The request is rejected because the message is either longer than the buffer

transmitted, it is odd, or it is smaller than the smallest value for a valid request image.

Recovery. The process has either destroyed the valid buffer or received an invalid

buffer. Correct the message byte count and resend the SPI message.

Additional Unconditional Tokens

ZMHS-TKN-XPNAME <1> token-type ZSPI-TYP-STRING.

ZEMS-TKN-EMPHASIS token-type ZSPI-TYP-BOOLEAN.

ZEMS-TKN-CONSOLE-PRINT token-type ZSPI-TYP-BOOLEAN.

Event-Message Text

SPI request from <1> bad: Invalid OCCURS value