Subsystem Control Point (SCP) Management Programming Manual

Introduction
Subsystem Control Point (SCP) Management Programming Manual—520619-001
1-2
The D-Series Environment
This manual presents the SCP process as a manageable subsystem, and describes:
For a detailed description of the role of SCP processes within the DSM environment, see
the SPI Common Extensions Manual.
The D-Series Environment
The features of the D-series Guardian operating system prompted several changes
relevant to SCP and related management processes. The D-series operating system
incorporates changes to improve CPU utilization and allow larger I/O configurations. In
part, these improvements were brought about by raising the limits on a number of
system parameters, thereby allowing:
•
More concurrent processes per CPU
•
More I/O devices per node
•
More I/O subdevices per device
•
More opens (concurrent access paths) per device and subdevice
•
More pending operations (outstanding messages)
In turn, these changes require the introduction of new and expanded data structures,
including:
•
New process identifiers
•
A new file name format
•
New SPI and EMS tokens corresponding to these new data structures
Finally, these new structures are supported by a set of new system procedures and
associated error numbers and error lists.
Summary of Changes
These changes directly affect programmatic management of SCP processes:
•
Management applications can use a new subsystem manager process identification
token (XMGR) to specify the process to which a command is sent.
•
SCP processes forward new requester identification (REQID) tokens to converted
subsystems.
Data definitions used by SCP processes Section 4, Common Definitions
The subset of the standard SPI commands supported
by SCP processes
Section 5, Commands and Responses
Event messages generated by SCP processes Section 6, Event Messages
Error messages generated by SCP processes Appendix A, Errors
The role of SCP processes in subsystem tracing Appendix B, Tracing