Mainframe Tape-to-Cloud Transfer via Block-Level Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in efficiently accessing and transferring data from mainframe tapes to cloud storage due to limitations in current Java interfaces, which restrict access to block-level information, require manual handling, and necessitate tape re-mounting for multiple reads, and lack efficient methods for writing data back to tapes or disks.
Innovation Solution
A method and system that allows data access and transfer between mainframe tapes and cloud storage using high-level languages like Java, enabling block-level reading and writing without changing the JOBCLASS parameter, allowing continuous tape access and using object storage to organize data without re-mounting, and supporting Large Block Interface for large data sets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored on tapes for long-term backup, then storage reliability and energy efficiency are improved, but data access time and operational complexity increase
Solution Approach 1:
The patent segments the data access process into multiple phases: initial tape mounting, sequential file reading through block-level interfaces, and automated tape management. This allows efficient processing of large datasets by breaking them into manageable blocks while maintaining the reliability benefits of tape storage for long-term backup.
Solution Approach 2:
The patent introduces an intermediary tape drive interface that bridges traditional tape storage and modern cloud storage systems. This intermediary enables block-level reading and writing operations, allowing data to be efficiently transferred from tapes to cloud storage without requiring manual handling or re-mounting, thus reducing access time while preserving backup reliability.
2Adaptability or versatility
If traditional Java interfaces are used for tape access, then system compatibility is maintained, but access to block-level information and operational efficiency are limited
Solution Approach 1:
The patent changes the interface parameters by implementing a new Java interface that supports block-level reading and writing operations on tapes. This interface provides methods for reading and writing data blocks, positioning tape drives, and managing tape operations, thereby enabling efficient data transfer while maintaining compatibility with existing Java-based mainframe systems.
3Loss of information
If multiple files are read from a mounted tape, then data completeness is improved, but operational complexity and time consumption increase due to required re-mounting
Solution Approach 1:
The patent enables continuous reading operations from a mounted tape by implementing sequential file access through block-level interfaces. The system can read multiple files and data blocks from the tape without requiring unmounting or re-mounting operations, thereby maintaining data completeness while significantly reducing operational complexity and time consumption.
4Speed
If tape drive technology is upgraded, then data access performance is improved, but system complexity and maintenance requirements increase
Solution Approach 1:
The patent creates a universal Java interface that can work with different tape drive technologies and configurations. This interface provides standardized methods for block-level reading, writing, and positioning operations, allowing the system to leverage upgraded tape drive hardware for improved data access speed while abstracting away the underlying complexity through a consistent programming interface.
Data Source
AI summary
Methods, system and computer program product, the method comprising: from high level language code (HLLC), receiving a request for reading a data set from a tape onto an object storage connected over TCP/IP to a mainframe; from the HLLC, allocating a data set on a tape comprising information to be imported, the allocation being in a format of the stored data set record and associated with a JFCB, the tape is mounted in SL mode; updating the JFCB to BLP mode; reading from the tape VOL1 data, and for each stored file initiating by the HLLC: reading HDR1/2, content block-by-block; EOF1/2 of the file; organizing the VOL1, HDR1, HDR2, content, EOF1 and EOF2 in the object storage; and closing the tape, wherein said reading is performed without setting a JES of the mainframe to BLP mode, and said reading is performed without unmounting the tape after each file.