What problem did SUPER-MSI solve?
SUPER-MSI was designed to eliminate hardware RESERVEs on shared DASD, enabling multiple z/OS systems to access and share datasets concurrently. It aimed to provide an alternative to GRS (Global Resource Serialization) for managing resource contention.
How was SUPER-MSI configured?
SUPER-MSI primarily used configuration files to define shared resources and access permissions. These files specified datasets, volumes, and systems participating in the sharing environment. The exact format and syntax of these files are not widely documented but were specific to the SUPER-MSI implementation.
What was the architecture of SUPER-MSI?
SUPER-MSI's architecture involved components running on each z/OS system participating in the shared DASD environment. These components communicated with each other to coordinate access and manage RESERVEs. Specific component names and communication protocols are not well-documented but were proprietary to the SUPER-MSI implementation.
How did SUPER-MSI improve system availability?
SUPER-MSI aimed to improve system availability by reducing contention for shared resources. By eliminating hardware RESERVEs, it allowed multiple systems to access datasets concurrently, minimizing delays and potential outages caused by resource contention.