Safeguard Management Programming Manual (G06.29+, H06.08+, J06.03+)

SPI Programming Considerations
Safeguard Management Programming Manual—422086-028
5-3
Error Handling
no value is specified for this token, the Safeguard subsystem returns a response
record for every object.
Error Handling
For general programming considerations for handling errors that occur when using the
management programming interfaces, see the SPI Common Extensions Manual.
In the programmatic control-and-inquiry interface to the Safeguard subsystem, the
return token (ZCOM-TKN-RETCODE) has two values that indicate that the response
record does not contain an error list. One value, ZCOM-ERR-OK, means that no error
occurred. (However, there might be an error list describing a warning). The other value,
ZCOM-ERR-EMPT-RSP, is an error number defined by the Safeguard subsystem that
signifies the empty response record. For example, this value is returned when an
application requests through ZSPI-TKN-RESPONSE-TYPE that only those response
records for objects on which errors or warnings occurred be returned, and the
command finishes executing without encountering any errors or warnings.
The Safeguard subsystem does not pass through errors from other subsystems or
interfaces.
For error-handling considerations for specific commands, see Section 7, Commands.
For the error numbers returned by the Safeguard subsystem, see Appendix A, Error
Numbers and Error Lists.
Security
$ZSMP provides its own security. No distinction is made between sensitive and
nonsensitive commands. However, access control lists can be used to restrict
unauthorized open requests to the SMP.
Note. For commands such as the INFO command, whose purpose is to return information,
using ZSPI-TKN-RESPONSE-TYPE to request the return only of those response records for
objects for which errors or warnings occurred can result in no information being returned.