SNAX/HLS Management Programming Manual

5 SPI Programming
Considerations for SNAX/HLS
104708Tandem Computers Incorporated 5–1
Applications use SPI procedures to build the command buffer and to extract data from
the response buffer.
Support of Security The SNAX/HLS subsystem controls its own security. The purpose of this security is
not to prevent unauthorized access (there is really nothing to protect), but rather to
prevent mistakes.
Three levels of security access are recognized: the highest level, a medium level, and
no security. The highest level of security access is required for switching the
SNAX/HLS process. Medium–level security access is needed for aborting sessions.
No other operation requires security.
The highest level of security access is given to any requester on the same node that
either has a SUPER.SUPER ID or has the same user ID as the SNAX/HLS process
itself.
Medium–level security access is given to any requester on the same node that either
has a SUPER.* ID or has the same group code as the SNAX/HLS process itself.
No security is assumed for a requester that is from a remote node or that fails one of
the user ID tests described above.