Mainframe Software Version Control via Dynamic Compatibility Levels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mainframe systems face challenges in managing software application version changes across multiple instances with varying compatibility levels, requiring a solution to ensure seamless updates and backward compatibility while maintaining system-wide reliability and security.

Innovation Solution

Dynamic release control identifies compatibility levels for software application instances, designates a common execution level, and configures instances to conform to it, allowing for automatic updates and compatibility level switches to maintain consistency and backward compatibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software application instances are updated to new versions with different compatibility levels, then system functionality and features are improved, but system stability and backward compatibility deteriorate

Engineering Contradiction:
Improvesoftware version flexibilityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic release control that automatically adjusts the common execution level based on the compatibility levels of updated software instances. The system monitors compatibility levels in real-time and dynamically reconfigures instances to maintain consistency, allowing the system to adapt to version changes while preserving stability through automated control mechanisms.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the execution level parameter of software application instances based on their compatibility levels. When instances are updated, the system modifies the common execution level parameter to match the lowest compatibility level among updated instances, ensuring that parameter changes maintain system-wide compatibility and prevent instability.

Inventive Principle:
Principle #35Parameter changes

2Manufacturing precision

If manual management of software version changes is performed across multiple instances, then compatibility control is precise, but operation complexity and time consumption increase

Engineering Contradiction:
Improvecompatibility control accuracyVSAvoidversion update time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements an automated release control system that self-manages software version updates across multiple instances. The system automatically identifies updated instances, determines their compatibility levels, adjusts the common execution level, and reconfigures instances without manual intervention, eliminating time-consuming manual operations while maintaining precise compatibility control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors the compatibility levels of software application instances and uses this feedback to automatically adjust the common execution level. When instances are updated, the system receives feedback about their new compatibility levels and automatically reconfigures the environment to maintain consistency, eliminating manual verification and control steps.

Inventive Principle:
Principle #23Feedback

3Productivity

If all software instances are updated simultaneously to the latest version, then system productivity is improved, but the risk of system-wide failures increases

Engineering Contradiction:
Improvesoftware update speedVSAvoidsystem failure risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent implements a protective mechanism where the system determines a common execution level based on the lowest compatibility level among updated instances before applying updates. This cushioning approach prevents system-wide failures by ensuring that no instance operates at an incompatible level, thereby eliminating the harmful effect of simultaneous updates while maintaining productivity through automated coordination.

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

4Stability of the object's composition

If compatibility level switching is performed across multiple instances, then system consistency is improved, but operation complexity increases

Engineering Contradiction:
Improvesystem consistencyVSAvoidcontrol mechanism complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent merges the compatibility level management of multiple software instances into a single common execution level. By consolidating individual instance compatibility levels into one system-wide execution level based on the lowest compatibility level, the system achieves consistency across all instances while simplifying control mechanisms, as only one execution level needs to be managed rather than individual levels for each instance.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9235402B2Dynamic release control of software application version changes
Publication Date: 2016.01.12 CA TECH INC
  • US9235402B2 patent drawing
  • US9235402B2 patent drawing
  • US9235402B2 patent drawing

AI summary

Dynamic release control is performed by identifying a plurality of software application instances installed on a mainframe system, identifying a compatibility level for each software application instance, designating a common execution level based upon a lowest one of the identified compatibility levels, configuring each software application instance to conform to the common execution level, receiving a software update indication that at least one software application instance has been updated and performing a compatibility level switch across the plurality of software application instances after receiving the software update indication if a lowest one of the compatibility levels is different from the common execution level by adjusting the common execution level based upon the lowest one of the compatibility levels and by reconfiguring each software application instance to operate in a mode that constrains the corresponding software application instance to conform to the adjusted common execution level.