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

Errors
SPI Programming Manual—427506-006
A-7
–9: ZSPI-ERR-ILLTKN
–9: ZSPI-ERR-ILLTKN
Cause. An invalid token code or token map was supplied in the procedure call. The
possibilities include:
•
The token data type was not recognized. For example, a program used a token
data type not included in the SPI standard definitions. (The only token data types
permitted by SPI are those defined by SPI.)
•
The token length was not a multiple of the basic length associated with the token
data type.
•
The token map contained an invalid null-value specification.
•
The sum of the lengths of the null-value specifications in the token map was not
equal to the total structure length specified by the map.
•
A token map was supplied as a parameter to SSGETTKN, SSPUTTKN, or
SSMOVETKN.
Any of these situations might arise if the program accidentally corrupted the variable
holding the token code or token map.
Effect. The last error is set to this error number, and the requested operation is not
completed.
Recovery. Correct the token code or token map causing the error.
–10: ZSPI-ERR-BADSSID
Cause. A subsystem ID with an invalid name was supplied as a parameter. The
owner-name field of a subsystem ID must contain an owner name that
•
Begins with an alphabetic character
•
Contains only alphabetic characters, hyphens, or numeric characters
•
Is left-justified and padded on the right with blanks
Effect. The last error is set to this error number, and the requested operation is not
completed.
Recovery. Check the ssid parameter being supplied in the call, and correct it as
necessary.
–11: ZSPI-ERR-NOTIMP
Cause. This operation is not supported in the version of the SPI definitions being
used. (For instance, the operation ZSPI-TKN-ADDR was called to get the address of a
header token.)
Effect. The last error is set to this error number, and the requested operation is not
completed.