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

General SPI Programming Guidelines
SPI Programming Manual—427506-006
5-15
Stopping the Management Process
Stopping the Management Process
Some subsystems have a special command to stop the management process
explicitly. Others stop this process automatically. Still others determine how they will
stop by reading the AUTOSTOP parameter sent as part of the startup message (see
Starting the Management Process
on page 5-9). For details, see the individual
subsystem management programming manual.
Maintaining Compatibility
For compatibility with future versions of HP software, your requester should:
•
Declare SPI buffers at least as large as the subsystems’ recommended sizes.
•
Tolerate unrecognized tokens in responses. (The simplest way to do that is to get
tokens only by name and avoid using NEXTCODE and NEXTTOKEN.)
•
Avoid beginning any of your own declared names with Z.
•
Call the SSNULL procedure to initialize the values of all extensible structured
tokens.
•
After calling SSNULL for each extensible structured token, set only token fields
that you use.
•
If your requester must communicate with several different versions of a subsystem,
including versions that are older than your requester, avoid sending any command,
token, or extensible-structured-token field that a subsystem does not support. If
necessary, use the GETVERSION command to check the server version and tailor
your command to it.
Responses to the GETVERSION command issued by a subsystem that has an
SPR must contain one instance of ZSPI-TKN-IPM-ID for each change to the SPI
interface for the subsystem. If more than one change affects the same token, the
ZSPI-TKN-IPM-ID for only the most recent change is returned. A subsystem might
also return a ZSPI-TKN-IPM-ID for a change that does not affect the SPI interface.
NonStop Kernel subsystems report errors if they receive commands, tokens, or
extensible-structured-token fields that they do not recognize. These errors are
described in the management programming manuals for the individual subsystems.
Summary of Requester Role
An SPI requester must:
•
Use subsystem-supplied definition files.
•
Declare a buffer at least as large as that recommended by the subsystem.
•
Use SSNULL to initialize all extensible structured tokens.