SPI Common Extensions Manual

ZCMK Definitions
SPI Common Extensions Manual—427508-001
B-76
–32745 ZCMK-EVT-SPI-NOT-CMD
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.
–32745 ZCMK-EVT-SPI-NOT-CMD
An SPI buffer was received that was not a valid command message.
ZEMS-TKN-EVENTNUMBER
has the value ZCMK-EVT-SPI-NOT-CMD.
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.
–32746 ZCMK-EVT-SPI-NO-HDR
The SPI header was missing.
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: Not a command message
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