External XML Validation for Mainframe Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing OS2200 system configurations require users to modify and recompile source code for validation rules, making the process time-consuming and error-prone, and necessitate separate verification steps after configuration is complete.

Innovation Solution

The use of an external Hardware Definition File (HDF) in XML format that embeds validation logic, allowing users to modify configuration rules without altering the source code, enabling real-time rule validation and eliminating the need for separate verification steps.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If validation rules are embedded in the source code of the verification application, then the validation logic is tightly integrated with the configuration program, but modifying validation rules requires recompiling and repackaging the source code which is time-consuming and error-prone

Engineering Contradiction:
Improvevalidation logic integrationVSAvoidrule modification efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the configuration management system into two independent parts: the configuration program (executable) and the validation rules (stored externally in XML files). This segmentation allows validation rules to be modified without affecting the program code, eliminating the need for recompilation and enabling rapid rule updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (XML validation rules file) between the configuration program and the validation logic. This intermediary stores validation rules externally and can be loaded dynamically, allowing rule modifications without changing the program source code or requiring recompilation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If validation rules are stored in an external XML file, then rule modification does not require source code changes and recompilation, but the validation program must load and parse the external file which adds complexity to the program

Engineering Contradiction:
Improverule modification efficiencyVSAvoidprogram structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-defining validation rules in XML files before they are needed. The configuration program loads these pre-defined rules into memory before execution, so that during normal operation, validation can proceed directly using the loaded rules without needing to parse external files in real-time, reducing the complexity of runtime operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a copy of the validation rules in an external XML file format that can be independently modified. This copy can be loaded into the program's memory space as needed, allowing rule changes without modifying the original program code or requiring complex runtime parsing operations.

Inventive Principle:
Principle #26Copying

3Ease of operation

If a separate verification application is used to validate configuration data, then configuration validation can be performed independently, but users must investigate and fix errors one-by-one which is time-consuming

Engineering Contradiction:
Improveconfiguration validation independenceVSAvoiderror correction time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements feedback by integrating real-time validation into the configuration program itself. As users input configuration data, the program immediately validates it against the XML rules and provides instant feedback on errors. This eliminates the need for separate verification steps and allows users to correct errors immediately without time loss.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent merges the configuration program and validation functionality into a single integrated system. The configuration program loads validation rules from external XML files and performs validation automatically during configuration entry, combining what were previously separate operations (configuration input and verification) into one unified process that eliminates sequential time loss.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS7475235B1Real-time management of a configuration of a computer system
Publication Date: 2009.01.06 UNISYS CORP
  • US7475235B1 patent drawing
  • US7475235B1 patent drawing
  • US7475235B1 patent drawing

AI summary

A computer system is described for representing and enforcing configuration rules that can be used to create and define a configuration or hardware definition for the computer system. The computer system represents configuration rules that define a configuration of a high end mainframe, such as an OS2200 system, in a file external to a configuration program with which a user may interact to manage the configuration of the mainframe system, and to enforce the configuration rules as a user is attempting to modify a configuration of a computer system. The configuration rules may be specified in, for example, an extensible markup language (XML) file format rather than in the source code of the executable program. The external configuration file may conform to a scripting language that allows a developer to embed validation operations for the configuration data specified in the XML file.