Shared Database Connection Across Mixed Addressability Modes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In batch execution environments, applications with programs of different addressability modes cannot share a database connection, leading to compromised transactionality due to the absence of resource managers.

Innovation Solution

An operating system service provides a shared database connection using database transactionality classes, such as Java archive files, to maintain transaction integrity between programs with different addressability modes, establishing connections on behalf of the application and managing transactions through resource managers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If programs with different addressability modes share a database connection in a batch environment, then interoperability and scalability are improved, but transactionality is compromised due to the absence of resource managers

Engineering Contradiction:

ImproveinteroperabilityVSAvoidtransactionality

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism (the operating system service with database transactionality classes) that mediates between programs with different addressability modes and the database. This intermediary establishes and manages shared database connections while ensuring transactionality is maintained, resolving the contradiction between enabling interoperability and preserving transactionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal database connection mechanism that can serve programs with different addressability modes (first and second addressability modes) through a single shared connection. The operating system service provides multi-functional support by managing transactions for diverse program types, thereby achieving both interoperability and transactionality.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If a shared database connection is established for programs with different addressability modes, then scalability is improved, but device complexity increases due to the need for operating system service intervention

Engineering Contradiction:

ImprovescalabilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service by allowing the operating system service to automatically establish and manage shared database connections for programs with different addressability modes. The database transactionality classes handle connection management autonomously, reducing the need for manual intervention and simplifying the overall system architecture despite the added functionality.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS12493613B2Method and apparatus for proving a shared database connection in a batch environment

Publication Date: 2025.12.09 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

An apparatus provides an operating system service that receives, from an application in a batch environment, a plurality of database transactionality calls associated with a first program of the application, the first program having a first addressability mode. In response to at least one of the plurality of database transactionality calls, the operating system service provides a shared database connection to a database for the first program of the application and for a second program of the application that has a different and second addressability mode. In some implementations, the operating system service provides the shared database connection using one or more of a plurality of callable database transactionality classes, such as a plurality of callable Java classes in a Java archive (JAR) file.