Smart Gatekeeper Data Validation for Mainframe Exchange Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy mainframe data processing systems face challenges with data consistency, resilience, real-time processing, data duplication, and lack of transparency, leading to inefficiencies, errors, and compliance issues, particularly in integrating with modern systems.

Innovation Solution

The Smart Gatekeeper (FGK) provides a platform-independent solution that converts legacy data formats to modern formats, performs real-time validation and security checks, ensures continuous operation across multiple data centers, and includes comprehensive audit and logging capabilities to maintain data integrity and consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If legacy mainframe systems process data in batches, then data volume handling capacity is improved, but data processing timeliness deteriorates

Engineering Contradiction:
Improvedata volumeVSAvoiddata processing delay
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system dynamically switches between batch processing and real-time processing modes based on system health and availability conditions. When the mainframe is healthy, real-time processing is enabled for immediate data handling. When failures are detected, the system automatically transitions to batch processing or alternative routing, allowing flexible adaptation to different operational states without being constrained to a single processing mode.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements periodic health checks and status monitoring of the mainframe system. These periodic assessments allow the system to detect failures promptly and switch processing modes accordingly, ensuring that data is processed in real-time when possible while maintaining system stability through scheduled monitoring intervals.

Inventive Principle:
Principle #19Periodic action

2Reliability

If data processing logic is embedded in application code, then data certainty control is improved, but system adaptability deteriorates

Engineering Contradiction:
Improvedata certaintyVSAvoidsystem flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system introduces an intermediary layer (the gatekeeper application) between the data sources and the mainframe processing logic. This intermediary implements the data certainty rules and validation logic externally, allowing the mainframe application code to remain unchanged while still enforcing data integrity. The intermediary acts as a mediator that can be independently modified and configured without affecting the core application logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments data processing into distinct modular components: data reception, validation, routing decisions, and processing execution. Each component is independently configurable and can be modified without affecting others. This segmentation allows data certainty rules to be applied in the validation stage while maintaining flexibility in the routing and processing stages through configuration files rather than code changes.

Inventive Principle:
Principle #1Segmentation

3Ease of manufacture

If files are processed at delivery location, then processing simplicity is improved, but system resiliency deteriorates

Engineering Contradiction:
Improveprocessing simplicityVSAvoidsystem resiliency
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The gatekeeper application serves multiple functions: it receives data from various sources, validates data integrity, monitors mainframe health status, makes routing decisions, and can redirect data to alternative processing locations. This multi-functional design allows the system to maintain simple processing logic while gaining resiliency through the ability to adapt routing based on system conditions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system performs preliminary health checks and availability assessments before routing data to the mainframe. By proactively monitoring system status and predicting potential failures, the gatekeeper can prevent data loss by redirecting data to alternative processing channels before a failure occurs, rather than reacting after a failure has impacted data processing.

Inventive Principle:
Principle #10Preliminary action

4Duration of action of stationary object

If mainframe systems ensure high availability, then service continuity is improved, but data processing resiliency deteriorates

Engineering Contradiction:
Improveservice continuityVSAvoiddata processing resiliency
Core Design Contradiction:
Duration of action of stationary objectVSReliability

Solution Approach 1:

The system implements beforehand cushioning by maintaining a buffer of monitored system health indicators and pre-configured alternative processing paths. When the mainframe is operating normally, data flows through the standard high-availability channel. However, the system has pre-prepared fallback mechanisms and alternative routing options that can be activated immediately upon detecting signs of system stress or failure, cushioning the impact before it affects data processing continuity.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS12541490B2Smart gatekeeper for data certainty
Publication Date: 2026.02.03 BANK OF AMERICA CORP
  • US12541490B2 patent drawing
  • US12541490B2 patent drawing
  • US12541490B2 patent drawing

AI summary

Systems and methods are disclosed for ensuring the integrity and security of data exchanges between mainframe systems and external channels. The invention includes a Data Distribution Service (DDS) that receives files from various channels and a Network Data Mover (NDM) that routes these files to a Gatekeeper Landing Zone (GK LZ) based on real-time server health and availability. A File Manager module detects new files, performs sanitization, converts files from EBCDIC to ASCII, and updates the Gatekeeper Control Database (GKC DB). The Validation module ensures data compliance, checks for duplicates, and logs exceptions. A Transaction Manager Resource Adapter (TMRA) splits data into transactions, identifies optimal processing paths, and converts data back to EBCDIC for transactions. The Reconciliation module verifies data accuracy and logs details, while the Backout module reverses transactions if discrepancies are found.