Selective Mainframe Resource Migration via Proxy Protocol Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge lies in enabling seamless data sharing and migration between mainframe and non-mainframe environments, particularly due to proprietary I/O systems in mainframes that are incompatible with open, standards-based client applications, making it difficult to access mainframe resources from non-mainframe platforms like cloud environments, and the complexity of transitioning applications without data integrity issues.

Innovation Solution

A system and method that employs a proxy to convert I/O requests between proprietary mainframe and standards-based protocols, enforce security and management policies, and enable data transformation and filtering, allowing client applications to access mainframe data while maintaining integrity and security, even across different architectures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a proxy is introduced to convert I/O requests between proprietary mainframe protocols and standards-based protocols, then compatibility and accessibility between mainframe and non-mainframe environments is improved, but system complexity increases due to the additional conversion layer

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A proxy server is introduced as an intermediary component between mainframe systems and non-mainframe clients. The proxy receives standards-based I/O requests from clients, converts them to proprietary mainframe protocols, executes the requests on the mainframe, and returns the results. This mediator resolves the protocol incompatibility without requiring changes to either the mainframe or the clients.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data transformation and filtering are performed to ensure consistency with standards-based protocols, then data integrity and compatibility are improved, but processing time and computational resources increase

Engineering Contradiction:
Improvedata integrityVSAvoiddata processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs data transformation and filtering operations in advance, before data is accessed by non-mainframe applications. Data is pre-transformed from proprietary mainframe formats to standards-based formats, and pre-filtered according to access patterns. This preliminary processing eliminates the need for repeated transformation operations during actual data access, reducing latency.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If security and management policies are enforced through the proxy, then security control and policy enforcement are improved, but operational complexity and management overhead increase

Engineering Contradiction:
Improvesecurity controlVSAvoidpolicy management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The proxy serves as a security intermediary that enforces mainframe security and management policies without requiring changes to client applications. It handles authentication, authorization, and policy compliance checks centrally, translating security requirements from the mainframe environment into access controls for standards-based clients. This centralizes security management while maintaining compatibility with diverse clients.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250225109A1System and method for selective migration of mainframe resources to a non-mainframe environment
Publication Date: 2025.07.10 VIRTUALZ COMPUTING CORP
  • US20250225109A1 patent drawing
  • US20250225109A1 patent drawing
  • US20250225109A1 patent drawing

AI summary

A method includes receiving, from a client device, an input/output (I/O) request pursuant to a first protocol, the first protocol being a standards-based I/O protocol. The I/O request is communicated to a proxy communicatively coupled with a mainframe server, the mainframe server being configured to communicate using a second protocol, the second protocol being a proprietary, mainframe protocol that is inconsistent with the first protocol. The method further includes accessing a database having a mapping of a plurality of I/O requests of the first protocol to a plurality of corresponding capabilities of the second protocol, and converting the I/O request pursuant to the first protocol to a corresponding capability pursuant to the second protocol. Security and management policies associated with the mainframe server are enforced using the proxy and the I/O request is executed on the mainframe server, using the corresponding capability pursuant to the second protocol. Data is received from the mainframe server, in response to the I/O request and it is determined whether the data requires transformation in order to be consistent with the first protocol. In response to determining that the data requires transformation, the data received from the mainframe server is transformed into a data format consistent with the first protocol, and the transformed data is communicated to the client device in response to the I/O request.