SPI Programming Manual (G06.24+, H06.03+, J06.03+)

Errors
SPI Programming Manual—427506-006
A-5
–4: ZSPI-ERR-BADADDR
with ZSPI-TKN-NEXTCODE or ZSPI-TKN-NEXTTOKEN unless you are certain
that all tokens the program could encounter are qualified by the default subsystem
ID.
•
The value parameter is required when calling SSGET with certain standard token
codes (such as ZSPI-TKN-LEN and ZSPI-TKN-OFFSET) or when calling SSPUT
with a token code that has a value (a nonzero token length).
Effect. ZSPI-TKN-LASTERR is set to ZSPI-ERR-MISPARM (unless the buffer
parameter is missing), and the requested operation is not performed.
Recovery. Supply the missing parameter.
–4: ZSPI-ERR-BADADDR
Cause. A reference parameter has an invalid address. Possibilities include:
•
A parameter has a starting address that is invalid or out of bounds.
•
A parameter has an absolute extended address, and the caller is nonprivileged.
•
A parameter's starting address and length are such that the parameter overlaps
the stack space required by the SPI procedure.
Effect. The header token ZSPI-TKN-LASTERR is set to this error number (unless the
bounds error occurs on the
buffer parameter), and the requested operation is not
performed. If the bounds error occurs on the
buffer parameter, SPI is unable to find
the buffer, so it cannot set ZSPI-TKN-LASTERR.
Recovery. Correct the parameter declarations to allocate the required amount of
storage.
–5: ZSPI-ERR-NOSPACE
Cause. One of:
•
The buffer is full; it cannot contain any more tokens or header information.
•
SSPUT was called with ZSPI-TKN-RESET-BUFFER, but maxlen was smaller
than the used length of the buffer. In this case, some information at the end of the
message was lost. Subsequent SPI calls for this buffer return error –1 (invalid
buffer format).
Effect. The last error is set to this error number, and the requested operation is not
completed.
Recovery. For the first, use a larger buffer. For the second, the corrective action
depends on the application.