File Control Block Synchronization for Cross-Mode Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Interoperability issues arise when computing programs using different addressing modes attempt to exchange information, leading to differences in memory addressability and linkage conventions, hindering seamless communication and execution.

Innovation Solution

A computer-implemented method is introduced that creates file control blocks in primary and secondary runtime environments with different addressing modes, synchronizing updates to ensure transparent and consistent input/output operations across environments, using anchors to link file control blocks and manage parameter passing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If programs use different addressing modes to maintain their native execution environments, then program compatibility and execution efficiency are improved, but interoperability between programs deteriorates

Engineering Contradiction:
Improveprogram execution efficiencyVSAvoidinteroperability between programs
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a secondary runtime environment as an intermediary between programs with different addressing modes. This intermediary translates file control block data structures between different addressing mode representations, enabling programs to execute in their native mode while interoperating through the mediating environment. The secondary runtime environment acts as a bridge that converts between addressing modes without requiring programs to change their native execution characteristics.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If file control blocks are created separately in different runtime environments with different addressing modes, then each program maintains its native data structure format, but data consistency and synchronization between environments deteriorate

Engineering Contradiction:
Improvenative data structure maintenanceVSAvoiddata consistency between environments
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the secondary runtime environment monitors and tracks file control block states across different runtime environments. When a program modifies a file control block in one environment, the changes are detected and propagated to the corresponding file control blocks in other environments. This feedback loop ensures data consistency is maintained while allowing each program to operate with its native data structure format.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If address translation and parameter passing mechanisms are implemented between different addressing modes, then interoperability is improved, but system complexity increases

Engineering Contradiction:
Improveinteroperability between programsVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the addressing mode translation functionality into a separate secondary runtime environment, isolating the complexity from the primary program execution paths. The translation mechanisms, including file control block conversion and parameter passing between different addressing modes, are contained within this dedicated environment. This segmentation allows programs to remain simple while the complex translation logic is handled by the specialized intermediary component.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11947993B2Cooperative input/output of address modes for interoperating programs
Publication Date: 2024.04.02 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11947993B2 patent drawing
  • US11947993B2 patent drawing
  • US11947993B2 patent drawing

AI summary

A computer-implemented method includes creating a first file control block in a primary runtime environment with a first addressing mode and a second file control block in a secondary runtime environment with a second addressing mode, where both the first file control block and the second file control block describe a status of a first file of a caller program in the primary runtime environment. The parameters of the first file of the caller program in the primary runtime environment are passed to a target callee program in the secondary runtime environment. An anchor is added in the first file control block as a link to the second file control block. The first file control block are the second file control block synchronized with updates to the first file in the primary runtime environment and the passed parameters of the first file in the secondary runtime environment.