Mapping Dynamic COBOL Constructs to Object Instances

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for integrating legacy COBOL data sets into object-oriented computing systems are inefficient and require custom coding to properly represent OCCURS DEPENDING ON and REDEFINE clauses, leading to increased costs and complexity.

Innovation Solution

A system integrator and method that maps dynamic COBOL constructs to object instances, using a client interface module, import module, object model module, and modeler module to generate customized object models that automatically represent OCCURS DEPENDING ON and REDEFINE clauses without the need for custom coding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If prior art approaches are used to integrate legacy COBOL data sets to object-oriented computing systems, then integration can be achieved, but the process is time consuming and expensive requiring human programmers to write custom code for each instance of OCCURS DEPENDING ON and REDEFINE clauses

Engineering Contradiction:

Improveautomation of COBOL to object-oriented integrationVSAvoidtime required for integration

Core Design Contradiction:

Extent of automationVSLoss of time

Solution Approach 1:

The system performs self-service by automatically identifying and mapping OCCURS DEPENDING ON and REDEFINE clauses without requiring human programmer intervention. The mapping engine autonomously analyzes COBOL copybooks and data sets, generating object-oriented representations through automated rule-based transformation processes.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary mapping engine that acts as a mediator between legacy COBOL systems and object-oriented computing systems. This intermediary component translates COBOL constructs including OCCURS DEPENDING ON and REDEFINE clauses into object-oriented equivalents, eliminating the need for manual custom coding while maintaining data integrity and structural relationships.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of manufacture

If prior art approaches are used to integrate legacy COBOL data sets, then integration can be achieved, but custom code must be written for each instance of OCCURS DEPENDING ON and REDEFINE clauses leading to increased complexity and cost

Engineering Contradiction:

Improveease of COBOL data set integrationVSAvoidcomplexity of integration process

Core Design Contradiction:

Ease of manufactureVSDevice complexity

Solution Approach 1:

The mapping engine implements universality by providing a single automated solution that handles multiple COBOL constructs including OCCURS DEPENDING ON clauses, REDEFINE clauses, and standard data structures. This multi-functional approach eliminates the need for separate custom code for each construct type, simplifying the integration process while maintaining comprehensive support for diverse COBOL data formats.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system applies parameter changes by dynamically adjusting mapping rules and transformation parameters based on the specific COBOL constructs encountered. The mapping engine automatically modifies its behavior to handle different clause types, data structures, and hierarchical relationships, enabling easy integration without requiring complex custom code for each scenario.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If prior art approaches are used, then COBOL data sets can be integrated, but the approach is unable to properly represent instances of OCCURS DEPENDING ON and REDEFINE clauses without human programmer intervention

Engineering Contradiction:

Improveaccuracy of COBOL construct representationVSAvoidease of representing COBOL constructs

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system achieves self-service by automatically and accurately representing OCCURS DEPENDING ON and REDEFINE clauses without human intervention. The mapping engine autonomously analyzes the controlling fields, determines occurrence values, and generates appropriate object-oriented representations that faithfully preserve the semantic meaning and structural characteristics of the original COBOL constructs.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical process of manual custom coding with an automated computational system. The mapping engine uses algorithmic rules and intelligent analysis to substitute human programmer efforts, automatically generating accurate representations of complex COBOL constructs through systematic processing rather than manual intervention.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10496702B2System integrator and method for mapping dynamic COBOL constructs to object instances for the automatic integration to object-oriented computing systems

Publication Date: 2019.12.03 AUREA SOFTWARE

AI summary

A system integrator for modeling an object instance of a COBOL data set, the object instance including representations of OCCURS DEPENDING ON clauses or REDEFINE clauses. The system comprises a client interface module, an import module, an object model module and modeler module. The client interface module generates an interface and receives a copybook selection and a set of REDEFINE criteria. The import module receives the copybook selection and imports a copybook from a database. The object model module receives the copybook and the set of REDEFINE criteria, and creates a customized object model for the copybook. The modeler module receives the customized object model and a set of COBOL data, and forms an object instance equivalent to the set of COBOL data, the object instance including representations of a OCCURS DEPENDING ON clause or REDEFINE clause.