DB2 Redirect Subsystem for Remote Mainframe Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current systems for accessing DB2 data from remote mainframes require multiple installations due to the need for local DB2 systems, leading to high costs and limitations in accessing data across different logical partitions, especially for legacy applications that cannot be easily modified.

Innovation Solution

A redirection subsystem that intercepts DB2 requests and normalizes them to allow access to remote DB2 systems, enabling communication via various telecommunication technologies without altering the business application programs or DB2 systems, and supports load balancing and failover capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple DB2 installations are deployed on different LPARs to enable remote access, then accessibility to DB2 data is improved, but system complexity and cost increase

Engineering Contradiction:

Improveremote access capabilityVSAvoidnumber of DB2 installations

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A redirect subsystem is introduced as an intermediary component that sits between the CICS subsystem and the DB2 database. This redirect subsystem intercepts DB2 connection requests from CICS and redirects them to the appropriate remote DB2 system, eliminating the need for local DB2 installations on each CICS LPAR. The redirect subsystem handles the complexity of remote connection management, allowing CICS to access DB2 data remotely without requiring multiple DB2 installations.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If documented APIs are used for DB2 access, then ease of operation is improved, but remote access capability is limited

Engineering Contradiction:

ImproveAPI usabilityVSAvoidremote access capability

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The redirect subsystem acts as an intermediary that transparently handles remote DB2 access while maintaining compatibility with documented APIs. When CICS subsystems use standard DB2 connection APIs, the redirect subsystem intercepts these requests and redirects them to remote DB2 systems. This allows legacy applications to continue using documented APIs without modification while enabling remote access capability that the APIs originally did not support.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of modifying the documented APIs to support remote access directly, the invention inverts the approach by introducing a redirect subsystem that sits between the API and the DB2 system. The redirect subsystem translates and redirects standard local DB2 connection requests to remote DB2 systems, effectively enabling remote access through the existing API interface without requiring API modifications.

Inventive Principle:

Principle #13The other way round (Inversion)

3Productivity

If DB2 system is moved between LPARs for load balancing, then system performance is improved, but application continuity is disrupted

Engineering Contradiction:

Improvesystem performanceVSAvoidapplication continuity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The redirect subsystem implements dynamic load balancing by monitoring the status and performance of multiple DB2 systems and dynamically redirecting CICS requests to the most appropriate available DB2 system. When a DB2 system is moved between LPARs or becomes unavailable, the redirect subsystem automatically detects this change and redirects traffic to alternative DB2 systems, maintaining application continuity while enabling performance optimization through load balancing.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The redirect subsystem changes the connection parameters dynamically based on the current state of DB2 systems. Instead of using fixed connection parameters, the redirect subsystem monitors DB2 system availability and performance, and adjusts the target DB2 system parameters in real-time. This allows the system to move DB2 instances between LPARs for load balancing while automatically updating connection parameters to maintain application continuity.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS10572553B2Systems and methods for remote access to DB2 databases

Publication Date: 2020.02.25 BMC SOFTWARE INC

AI summary

Systems and methods are provided that allow client programs using APIs for accessing local DB2 databases to access DB2 systems on remote logical partitions and remote zSeries mainframes rather than from a local DB2 system. For example, a method may include intercepting a DB2 request using a documented API for accessing local DB2 databases from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, a DB2 connection with the DB2 system from the request. The method may further include receiving a response from the DB2 system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.