SNAX/HLS Management Programming Manual

ZCOM Data Communications Errors
Error Numbers and Error Lists
A–8 104708 Tandem Computers Incorporated
ZCOM Data
Communications
Errors
SNAX/HLS may return the following ZCOM data communications errors:
–4: ZCOM–ERR–CMD–MISMATCH
–5: ZCOM–ERR–CMP–NOT–SUPP
–17: ZCOM–ERR–OBJ–NOT–FOUND
–22: ZCOM–ERR–SECUR–VIOL
–23: ZCOM–ERR–SPI–ERR
–24: ZCOM–ERR–SSID–INV
–26: ZCOM–ERR–TKN–CODE–INV
–27: ZCOM–ERR–TKN–DUP
–29: ZCOM–ERR–TKN–REQ
–30: ZCOM–ERR–TKN–VAL–INV
–32: ZCOM–ERR–VSN–INCOMP
–33: ZCOM–ERR–EMPT–RSP
–36: ZCOM–ERR–TKN–CNTXT–VAL–INV
These errors are described in detail in the Communications Management Programming
Manual, with the exception of ZCOM–ERR–EMPT–RSP and
ZCOM–ERR–TKN–CNTXT–VAL–INV. The descriptions of these two errors follow.
–33: ZCOM–ERR–EMPT–RSP
This value is returned in the token ZSPI–TKN–RETCODE to indicate that although the
command was successfully processed, no responses were generated. This happens, for
example, when the token ZSPI–TKN–RESPONSE–TYPE has the value
ZSPI–VAL–ERR–AND–WARN and no warnings or errors are generated.
This error number does not have an error list associated with it.
Cause. The command was successfully processed; no responses were generated.
Effect. Information only.
Recovery. Because this message does not indicate an error; no recovery action is
needed.