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

SPI Concepts and Protocol
SPI Programming Manual—427506-006
2-51
Recovering From an Error on an Object in a Set
subsystems that do not support this feature do not proceed to the next object in the set
if any error or warning occurred on the previous object.
Recovering From an Error on an Object in a Set
The use of the context token for continuation allows for resuming processing after an
error, starting with the object following the one on which the error occurred. That
makes it easy for your application to continue the command immediately.
If preferred, your application can instead correct the problem that caused the error and
have the command continue with the object that got the error. If the server is context
free, the requester can issue any number of commands between the receipt of a
response with a context token and the sending of the continuation that includes that
context. Your application can correct the problem immediately by issuing commands
naming the particular object that failed. When everything is resolved for that object
(including sending a command duplicating the original command that failed, but
directed just to that one object), your application can use the context token to continue
the original command with the next object.
Sample Error Responses
In these examples, indenting shows the nesting levels of error lists and the names of
fields within fixed structures.
Error List Example 1
A simple error response from subsystem SYSB:
<ZSPI-TKN-RETCODE> ! n (command not
supported)
<ZSPI-TKN-ERRLIST>
<ZSPI-TKN-ERROR>
Z-SSID ! Subsystem ID for SYSB
Z-ERROR ! n (command not
supported)
<SYSB.ZSPI-TKN-ENDLIST> ! end of error list
In this example, subsystem SYSB returns a nonzero return code indicating that it does
not support the command specified by the requester in the original request. The
Z-ERROR field of the error token in the corresponding error list has the same error
number, indicating that it contains information about the error.