Cloud Gateway Translating SQL to DL/I for IMS Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based applications face processing delays and increased costs when accessing legacy data stored in IBM IMS databases due to the lack of dedicated hardware and predefined environments for API calls, which are typically handled by middleware like IBM WebSphere and DataPower.

Innovation Solution

A system that translates SQL calls from cloud-based applications into DL/I calls and transmits them to IMS databases via IMS Connect, allowing direct access and reducing response time by eliminating the need for middleware intermediaries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If middleware (IBM WebSphere, DataPower, IMS OTMA) is used to access IMS databases from cloud-based applications, then compatibility and data access capability are improved, but processing time increases (2 seconds or longer) and costs increase

Engineering Contradiction:
Improvedata access capabilityVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts and removes the middleware layer from the data access path. By implementing a direct connection mechanism between cloud-based applications and IMS databases, it eliminates the intermediate processing steps through WebSphere, DataPower, or OTMA, thereby reducing processing time from 2 seconds or longer to a significantly faster direct access pathway while maintaining full data access capability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a new intermediary component that sits between cloud-based applications and IMS databases. This intermediary provides the necessary protocol translation and environment emulation directly at the database interface level, allowing SQL-based cloud applications to access hierarchical IMS databases without the overhead of traditional middleware, thus resolving the time-cost contradiction

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If middleware is used to facilitate API calls to IMS databases, then data access functionality is improved, but processing delays and costs increase

Engineering Contradiction:
Improvedata access functionalityVSAvoidprocessing efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent merges the data access functionality and protocol translation capabilities directly into the database connection interface. By combining these functions at the IMS database level rather than through separate middleware components, it maintains ease of operation for cloud-based applications while significantly improving processing efficiency by eliminating redundant processing steps

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal access mechanism that handles multiple data access operations (API calls, SQL queries, hierarchical data access) through a single direct connection pathway. This multi-functional interface replaces the need for separate middleware components, maintaining operational ease while boosting overall processing efficiency

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of manufacture

If cloud-based applications use standard SQL calls, then ease of development is improved, but direct compatibility with hierarchical IMS databases deteriorates

Engineering Contradiction:
Improveease of developmentVSAvoiddatabase compatibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary layer at the database interface that performs protocol translation. This intermediary receives standard SQL calls from cloud-based applications and automatically translates them into the hierarchical data access protocols required by IMS databases, thereby maintaining ease of development with SQL while achieving full compatibility with the target database system

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the interface parameters and protocol specifications at the database connection level. By implementing parameter translation that converts SQL-based requests into hierarchical database commands, it allows cloud-based applications to use familiar SQL syntax while maintaining full compatibility with IMS database structures, resolving the contradiction between development ease and database adaptability

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10673982B2Cloud-based application communication with hierarchical databases
Publication Date: 2020.06.02 AMERICAN EXPRESS TRAVEL RELATED SERVICES CO INC
  • US10673982B2 patent drawing
  • US10673982B2 patent drawing
  • US10673982B2 patent drawing

AI summary

A gateway may allow for a cloud-based application to connect to a hierarchical type database. The gateway may identify a connection route between a cloud instance and the hierarchical type database. The gateway may translate a SQL call from the cloud-based application to a DL/I call to access data on the hierarchical type database.