SPI Common Extensions Manual
ZCMK Definitions
SPI Common Extensions Manual—427508-001
B-75
–32743 ZCMK-EVT-SPI-SHORT
Recovery. The requester should re-create and send a valid message buffer.
–32743 ZCMK-EVT-SPI-SHORT
A received SPI command buffer was too short to be valid.
ZEMS-TKN-EVENTNUMBER
has the value ZCMK-EVT-SPI-SHORT.
ZCMK-TKN-XPNAME
contains the name of the process that issued the short 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.
–32744 ZCMK-EVT-SPI-NOT-MSGCODE
An SPI command message was received without the message code -28 in the first
2 bytes of the buffer.
ZEMS-TKN-EVENTNUMBER
has the value ZCMK-EVT-SPI-NOT-MSGCODE.
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: Message short
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: Code word not -28