Expand Management Programming Manual

SPI PROGRAMMING CONSIDERATIONS FOR THE EXPAND SUBSYSTEM
Error Handling
ERROR HANDLING
General programming considerations for handling errors that occur
when using the management-programming interfaces are discussed in
the Communications Management Programming Manual .
In the programmatic control-and-inquiry interface to the EXPAND
subsystem, there are two values for the return token that
indicate that the response record does not contain an error
list. One is the value ZSPI-ERR-OK, which means that no error
or warning occurred. The other is an error number defined
by the EXPAND subsystem that signifies the "empty" response
record. This value, ZEXP-ERR-EMPT-RSP, is returned, for example,
when an application requests through ZSPI-TKN-RESPONSE-TYPE that
only response records for objects on which errors or warnings
occurred be returned, and the command finishes processing without
encountering any errors or warnings.
The EXPAND subsystem does not pass through errors from other
subsystems or interfaces.
Error-handling considerations for specific commands are described
in Section 7, "Commands and Responses." The error numbers
returned by the EXPAND subsystem are described in Appendix A.
SECURITY
Security for the EXPAND subsystem is handled by SCP, as described
in the Communications Management Programming Manual .
Some of the EXPAND commands are sensitive commands, meaning that
they can be issued only by certain users (for EXPAND, members of
the SUPER group and members of the same group as the owner of the
EXPAND manager process). When an application that is not allowed
to issue sensitive commands attempts to issue one, SCP returns
an error. For more information on sensitive commands, refer to
Section 7, "Commands and Responses."
5-4