Subsystem Control Point (SCP) Management Programming Manual
SPI Programming Considerations for SCP
Subsystem Control Point (SCP) Management Programming Manual—520619-001
3-10
SCP and the ZCMK Definitions
SCP and the ZCMK Definitions
The SCP process is based on the ZCMK definitions described in the SPI Common
Extensions Manual. This subsection highlights some implications of this.
ZCMK Command and Response Tokens
Commands sent to and responses generated by an SCP process can contain ZCMK
tokens. For descriptions of each token, see the SPI Common Extensions Manual and
specific command descriptions in Commands and Responses
on page 5-7.
Further, commands sent to a subsystem process that is based on the ZCMK definitions
can accept additional ZCMK tokens if the object specified in the command is the
management process itself, as when you are trying to manage an SCP process. (Such a
process—responsible for performing SPI management functions on behalf of the
subsystem—is called the subsystem’s native object, and the object type assigned to it is
called the native object type. In some subsystems, this is a separate process. In the case
of SCP, a single process performs both management functions and subsystem functions.
The native object type of the SCP process is ZCOM-OBJ-PROC.)
File Names in Commands and Responses
File names included in commands sent to an SCP process should be fully qualified. The
SCP process completes any missing part of the name, using the local node and
$SYSTEM.SYSTEM as the default.
File names returned in a response buffer by an SCP process are fully qualified and in
string format (token-type ZSPI-TKN-STRING). The node name is included if the node
has a name.
SCP Request Validation
Like all ZCMK-based processes, SCP processes perform a common set of tests to
validate a request buffer and its contents. These tests fall into four basic categories:
•
SPI buffer validation
•
General request validation
•
Token occurrence and value tests
•
Special tests
For a description of these tests, see the SPI Common Extensions Manual.