Storage Volume Slot Management for Mainframe Open-Architecture Interoperation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for interoperation between mainframe systems and open-architecture systems require separate storage, leading to burdensome hardware and system development costs.
Innovation Solution
A storage system that includes a storage device, a processor, and a storage unit, where the processor configures volumes on the storage device to provide functionality to mainframe servers, manages data using slots of different lengths, and performs processes based on the type of process, thereby integrating open-architecture system functions into mainframe systems at a lower cost.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate storage is provided for interoperation between mainframe systems and open-architecture systems, then interoperation functionality is achieved, but hardware and system development costs become burdensome
Solution Approach 1:
The patent merges the storage resources of mainframe systems and open-architecture systems into a single shared storage pool. The storage device is configured to simultaneously support both mainframe servers (via FCP protocols) and open-architecture servers (via iSCSI protocols), eliminating the need for separate storage systems and reducing hardware complexity and costs while maintaining interoperation functionality.
Solution Approach 2:
The storage device is designed with multi-functionality to serve dual purposes: it acts as a storage device for mainframe servers through FCP protocol support and as a storage device for open-architecture servers through iSCSI protocol support. This universal design allows a single storage system to fulfill multiple roles, reducing the need for separate specialized storage systems.
2Adaptability or versatility
If data is managed using different slot lengths for open-architecture servers and mainframe servers, then compatibility with both systems is achieved, but storage management complexity increases
Solution Approach 1:
The storage device divides its storage space into distinct slot types: open-architecture slots (e.g., 8KB) for open-architecture servers and mainframe slots (e.g., 32KB) for mainframe servers. Each slot type is optimized for its corresponding system architecture. The management unit maintains separate mapping tables to track the location and status of each slot type, enabling independent management of each slot category while presenting a unified storage interface to both server types.
Solution Approach 2:
Different regions or portions of the storage device are optimized with different slot characteristics tailored to specific system requirements. Open-architecture data resides in slots optimized for 8KB alignment, while mainframe data resides in slots optimized for 32KB alignment. This local optimization allows each system type to access data in its preferred format without interfering with the other, reducing management complexity through localized specialization.
Data Source
AI summary
A storage system includes a storage device, a processor, and a storage unit. The processor provides a volume configured on the storage device to a mainframe server. The processor manages data handled by an open-architecture server, using a first slot having a first slot length as a unit, in the volume, and manages data handled by the mainframe server, using a second slot having a second slot length shorter than the first slot length as a unit, the first slot storing therein a predetermined number of the second slots, in the volume. The processor performs a process using one of the first slot and the second slot as a unit, depending on the type of the process.