Legacy-Open Data Mapping for Stable Mainframe Modernization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy systems, such as mainframe computers, face challenges in modernization due to inherent limitations of programming languages like COBOL and RPG, including inability to handle modern data formats and memory allocation, leading to a scarcity of skilled programmers and difficulties in migrating to open technologies.

Innovation Solution

A method and system for data conversion that enables legacy programs to be invoked by open systems, using a broker to convert data formats automatically and allow access to dynamically allocated memory, facilitating the use of modern data structures without modifying the legacy programs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If legacy systems use traditional programming languages (COBOL, RPG), then reliability and stability are maintained, but adaptability to modern data formats and technologies deteriorates

Engineering Contradiction:
Improvesystem stabilityVSAvoiddata format compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a data translator as an intermediary component that converts data between legacy COBOL formats and modern open formats (JSON, XML). This translator layer allows legacy systems to maintain their stable operation while gaining compatibility with modern data formats, resolving the contradiction between reliability and adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the legacy mainframe environment from the modern open environment through intermediate storage areas and protocol translators. This segmentation allows each environment to operate in its optimal format while exchanging data through standardized interfaces, maintaining stability in the legacy system while enabling adaptability in the modern environment.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If legacy systems are migrated to open technologies, then adaptability and modernization are improved, but reliability and proven performance deteriorate

Engineering Contradiction:
Improvetechnology modernizationVSAvoidperformance consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a segmented architecture where legacy COBOL programs continue to execute on the mainframe in their proven environment, while modern open applications run separately. The segmentation through intermediate storage and protocol translators ensures that performance and reliability remain with the legacy systems while modernization occurs in the open environment layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The protocol translator acts as an intermediary that preserves the proven performance characteristics of legacy COBOL programs while enabling them to interface with modern open technologies. This ensures that migration to open technologies improves adaptability without sacrificing the reliability and performance consistency of the core business logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If data structures are converted manually, then format compatibility is achieved, but loss of time and human labor increase

Engineering Contradiction:
Improveformat compatibilityVSAvoidconversion time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements self-service through automated protocol translation. The system automatically translates data between COBOL and open formats without requiring manual intervention. The translator uses configuration files to define conversion rules, enabling the system to self-convert data formats autonomously and reducing both time loss and human labor.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The automated protocol translator serves as an intermediary that handles data format conversion automatically. Rather than manual conversion, the translator uses predefined mapping rules to autonomously convert data structures, significantly reducing conversion time and human effort while maintaining format compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If legacy programs are modified to support modern formats, then adaptability is improved, but device complexity and programming difficulty increase

Engineering Contradiction:
Improvedata format supportVSAvoidprogram complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a protocol translator as an intermediary that handles all data format conversion logic externally to the legacy programs. This allows legacy COBOL programs to remain simple and unchanged while the translator manages the complexity of converting between COBOL and modern formats, thus improving adaptability without increasing program complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the data format conversion functionality from the legacy programs and places it in a separate translator component. This extraction removes the complexity of format handling from the business logic, allowing legacy programs to maintain their simplicity while the system gains modern format support through the external translator layer.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20260079959A1A system and method for inter-operation of legacy and open computing environment
Publication Date: 2026.03.19 Z2OPEN LTD
  • US20260079959A1 patent drawing
  • US20260079959A1 patent drawing
  • US20260079959A1 patent drawing

AI summary

A method, system and computer program product, the method comprising: interpreting data in a first environment structure of first format used in a first environment to a second structure of second format used in a second environment, the interpreted data stored in an intermediate storage; activating a program for using data from the intermediate storage to produce output to be stored in a second intermediate storage; and upon program termination, interpreting the output from the second to the first structure, wherein interpreting the data and the output is performed using a mapper between the first and the second formats, wherein the formats are different in that a field in the first format is absent in the second, or vice versa, or in that a field in the first format is formatted differently in the second, or fields in the second format have different order from fields in the first format.