SPI Common Extensions Manual

ZCMK Definitions
SPI Common Extensions Manual—427508-001
B-77
–32747 ZCMK-EVT-SPI-BAD-OCCURS
ZEMS-TKN-EVENTNUMBER
has the value ZCMK-EVT-SPI-NO-HDR.
ZCMK-TKN-XPNAME
contains the name of the process that issued the request.
Cause. The requester might have corrupted a valid SPI buffer, lost track of where the
buffer was built, or sent the wrong data.
Effect. The request is rejected with file-system error 2 (ZFIL-ERR-INVALOP).
Recovery. The requester should re-create and send a valid message buffer.
–32747 ZCMK-EVT-SPI-BAD-OCCURS
An SPI buffer was received with a byte count that cannot occur in a well-formed
message.
ZEMS-TKN-EVENTNUMBER
has the value ZCMK-EVT-SPI-BAD-OCCURS.
ZCMK-TKN-XPNAME
contains the name of the process that issued the request.
Cause. The buffer’s byte count is greater than the actual length of the buffer, is odd
(not even), or is smaller than any valid command message. The requester might have
corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong
data.
Effect. The request is rejected with file-system error 2 (ZFIL-ERR-INVALOP).
Recovery. The requester should re-create and send a valid message buffer.
Message Text
<1>: SPI Request from <2> bad: No header
Tokens in Event Message
ZEMS-TKN-EVENTNUMBER token-type ZSPI-TYP-ENUM
ZEMS-TKN-SUBJECT-MARK token-type ZSPI-TYP-MARK
ZCOM-TKN-SUBJ-objtype <1> token-type ZSPI-TYP-STRING
ZCMK-TKN-XPNAME <2> token-type ZSPI-TYP-STRING
Message Text
<1>: SPI Request from <2> bad: Invalid OCCURS value