Header Trailer Validation Tool for Batch Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual and labor-intensive process of validating header and trailer records in batch files is time-consuming and requires individual processing in each program, lacking efficient integrity verification.

Innovation Solution

A computer-implemented system and method for header and trailer validation in batch files, utilizing a memory interface, interactive interface, and processor to dynamically read files, identify formats, and confirm record integrity without altering existing programs, enabling flexible and efficient validation across multiple applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual code writing for header and trailer record validation is performed in each individual program, then validation functionality is achieved, but development time and labor intensity increase significantly

Engineering Contradiction:
Improveheader and trailer record validationVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The validation logic is extracted from individual programs into a separate, reusable component. The system reads control cards that define validation rules and applies them independently to each batch file, separating the validation functionality from the main program logic. This allows validation to be performed without modifying existing programs.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

A universal validation framework is implemented that can handle multiple file formats and validation rules through control cards. The same validation mechanism works across different applications and file types by simply changing the control card parameters, eliminating the need to write custom validation code for each program.

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

2Reliability

If individual validation code is added to every program, then header and trailer validation is implemented, but the complexity of the system increases

Engineering Contradiction:
Improvefile integrity verificationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Validation complexity is extracted into a separate control card-based system. Instead of embedding validation logic within each program, the system uses external control cards to define validation rules, keeping the main programs simple and reducing overall system complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Control cards serve as an intermediary between the validation requirements and the processing logic. They provide a configuration layer that separates the complexity of validation rules from the execution logic, making the system easier to manage and modify.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If manual validation processing is performed for each batch file, then record integrity can be verified, but processing time and labor requirements increase

Engineering Contradiction:
Improveintegrity verificationVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs self-service validation by automatically reading control cards and applying validation rules without manual intervention. The validation process is automated through the control card mechanism, which allows the system to configure and execute validation independently for each file.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Validation rules are prepared in advance in control cards before processing batch files. This preliminary configuration allows the system to efficiently apply pre-defined validation logic during file processing, eliminating the need for manual validation setup and improving processing efficiency.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If validation code is added to existing programs, then header and trailer validation is achieved, but regression testing requirements increase

Engineering Contradiction:
Improvevalidation capabilityVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Validation functionality is extracted into a separate, independent component that does not modify existing programs. This separation ensures that adding validation capability does not affect existing program functions, eliminating the need for extensive regression testing.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10884983B2Method and system for implementing header and trailer record validations
Publication Date: 2021.01.05 JPMORGAN CHASE BANK NA
  • US10884983B2 patent drawing
  • US10884983B2 patent drawing
  • US10884983B2 patent drawing

AI summary

The invention relates to header and trailer record validation for batch files. According to an embodiment of the present invention, a computer implemented system implements a Header/Trailer Validation Tool. The Header/Trailer Validation Tool may read a control file containing pertinent information of each file to be validated. Key information may be determined at run time and the Header/Trailer Validation Tool may process the files dynamically. An embodiment of the present invention may also process any number of files in a single execution—this is particularly useful because in some cases a set of files may be received from another application, but not all the files may be used at the same time.