HP Guardian Errors Manual page 212

The program supplied an SPI-defined token code that was invalid for this procedure call. For
example, ZSPI-TKN-DELETE was specified in a call to SSGET, or ZSPI-TKN-COMMAND was
specified in a call to SSPUT.
An invalid position descriptor was supplied with ZSPI-TKN-POSITION.
Effect The header token ZSPI-TKN-LASTERR is set to this error number, and the requested operation
is not completed.
Recovery Correct the parameter in error.
-3 ZSPI-ERR-MISPARM
Cause This error number indicates that a required parameter was not supplied. Certain parameters
are required only under certain circumstances:
The ssid parameter is required when calling SSGET with ZSPI-TKN-NEXTCODE or
ZSPI-TKN-NEXTTOKEN if the next token code in the buffer is not qualified by the default
subsystem ID. Always supply a variable for ssid when calling SSGET 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 The header token ZSPI-TKN-LASTERR is set to this error number (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 illegal address for one of the following reasons:
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 that is required by the SPI procedure.
An extended-address parameter refers to the current code space. This can occur if the parameter
is a read-only array located in a user-library space.
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 storage.
-5 ZSPI-ERR-NOSPACE
Cause This error can occur for one of the following reasons:
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 will return error - 1 (invalid buffer format).
212 Subsystem Programmatic Interface (SPI) Errors
Missing parameter
Illegal parameter address
Buffer full