Source Code Synchronization Between Mainframe and Distributed Environments

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Financial institutions face challenges in maintaining separate mainframe environments across different geographic locations to comply with regulations, leading to inefficiencies and high costs due to disparities in source code management processes between mainframe and distributed environments.

Innovation Solution

Implementing a version control repository to synchronize and manage a single source codebase across divergent computing environments, using tools like Git or Bitbucket to track changes and propagate updates from the mainframe environment to the distributed environment, ensuring compliance with local data storage regulations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate mainframe environments are maintained across different geographic locations to comply with regulations, then compliance with local data storage regulations is improved, but operational costs and complexity increase due to disparities in source code management processes

Engineering Contradiction:

Improvecompliance with local data storage regulationsVSAvoidsource code management process disparity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the source code management process into distinct phases: mainframe development phase and distributed environment deployment phase. By maintaining a single source codebase in the mainframe environment and selectively synchronizing only changed files to the distributed environment, the system achieves regulatory compliance while reducing operational complexity through phased management rather than parallel maintenance.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a version control system as an intermediary between the mainframe environment and distributed environment. This intermediary tracks changes in the mainframe source codebase and facilitates selective synchronization, enabling compliance with local data storage regulations while unifying the source code management process and reducing operational complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If a single source codebase is used across mainframe and distributed environments, then operational costs are reduced and efficiency is improved, but challenges arise from disparities in build and deployment processes between divergent computing environments

Engineering Contradiction:

Improveoperational efficiencyVSAvoidbuild and deployment process disparity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent applies local quality by allowing each computing environment to have its own build and deployment processes tailored to its specific requirements, while both environments share a common source codebase. The version control system enables each environment to manage its build/deployment independently without affecting the other, thus maintaining operational efficiency while accommodating environmental disparities.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements universality through a single source codebase that serves multiple functions: it is the source of truth for both mainframe and distributed environments, enabling selective synchronization of changed files. This universal source codebase eliminates the need for separate maintenance processes while allowing each environment to have customized build and deployment workflows.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If changes to mainframe source code files are synchronized to distributed environment, then code consistency across environments is improved, but time and resources are consumed by tracking and propagating changes

Engineering Contradiction:

Improvecode consistency across environmentsVSAvoidtime for tracking and propagating changes

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent implements periodic action through event-driven synchronization, where changes in the mainframe source codebase are detected and propagated to the distributed environment at appropriate intervals or when specific events occur (e.g., file modification, commit to version control). This periodic mechanism maintains code consistency while minimizing the time and resources consumed by tracking and propagating changes only when necessary.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The patent applies self-service through automated change tracking and synchronization mechanisms. The version control system automatically detects changes in the mainframe source codebase and triggers synchronization to the distributed environment without manual intervention. This self-service approach maintains code consistency across environments while reducing the time and human resources required for manual tracking and propagation.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS10846081B2System and method for code synchronization between mainframe environment and distributed environment

Publication Date: 2020.11.24 MASTERCARD INT INC

AI summary

Systems and methods are provided for using of a single source codebase synchronized between two divergent computing environments. In some embodiments, a version control repository may be utilized to track changes to mainframe source code and synchronize the changed mainframe source code files with a set of source code files stored in the version control repository.