Subsystem Control Point (SCP) Management Programming Manual

Commands and Responses
Subsystem Control Point (SCP) Management Programming Manual—520619-001
5-7
Command Security
Command Security
SCP enforces basic command security on the basis of the distinction between sensitive
and nonsensitive commands.
A command capable of affecting SCP’s operation in any way is called a sensitive
command. This includes any command that can change the summary state, status, or
configuration of an SCP process.
A command that retrieves information about an SCP process without affecting the
process in any way is called a nonsensitive command. An application with any access ID
can issue nonsensitive commands.
An SCP process accepts a sensitive command only from a requester that satisfies one of
these requirements:
•
The requester belongs to the super group.
•
The requester has the same ID as the creator access ID (CAID) of the SCP process.
This is true if the requester started the SCP process; therefore, a requester can
always issue sensitive commands to an SCP process that it has started.
Requester Identification
SCP accepts REQID tokens in a command, but only if the requester belongs to the super
ID. If a qualified requester includes REQID tokens in a command, SCP forwards those
tokens to the subsystem. This lets management applications funnel requests from other
requesters through SCP to the subsystem.
Commands and Responses
Commands are listed in alphabetical order. Each command description includes:
•
A description of the command
•
The command number
•
A list of the tokens in the command message and the response
•
A description of any token not previously described in Common Command Tokens
on page 5-2 or Common Response Tokens on page 5-5.