CICS Program Deployment via API Call Interception

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The CICS transaction processing system does not support automated program deployment, requiring manual intervention that is time-consuming and error-prone, leading to outages and interruptions in business-critical applications.

Innovation Solution

A method is introduced to install a program within a CICS region without an antecedent program by intercepting and executing API calls, using a program launching module to schedule an interrupt request block and transition control from the host operating system to the CICS region, allowing the CICS region to execute API calls as if they are part of a service call, thereby bypassing the need for manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual program deployment is used in CICS, then program installation can be performed, but it requires manual intervention that is time-consuming and error-prone

Engineering Contradiction:
Improveerror-free deploymentVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service automated program deployment within CICS regions. The program deployment module automatically intercepts API calls, schedules interrupt request blocks, and executes program installation without requiring manual operator intervention, thereby eliminating human errors and reducing deployment time while maintaining system reliability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by intercepting API calls before program installation is attempted. The interrupt request block is scheduled in advance, and control transition mechanisms are prepared beforehand, allowing the deployment process to execute automatically and efficiently without manual intervention during the actual installation

Inventive Principle:
Principle #10Preliminary action

2Productivity

If manual intervention is required for program deployment, then control can be managed, but it leads to outages and interruptions in business-critical applications

Engineering Contradiction:
Improveapplication availabilityVSAvoidmanual control
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system performs self-service automated deployment operations within the CICS region. The program deployment module automatically manages control transitions, intercepts necessary API calls, and executes installation procedures without requiring manual operator control, thereby maintaining high application availability while eliminating the need for manual intervention that causes outages

Inventive Principle:
Principle #25Self-service

3Productivity

If automated program deployment is implemented, then deployment speed increases, but it requires intercepting and executing API calls without antecedent program

Engineering Contradiction:
Improvedeployment speedVSAvoiddeployment mechanism
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary program deployment module that acts as a mediator between the host operating system and the CICS region. This module intercepts API calls and manages the complex control transition process, thereby enabling automated deployment without requiring changes to the core CICS infrastructure or antecedent programs, thus maintaining deployment speed while managing complexity through a dedicated intermediary component

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12164897B2Deploying a program from within an active CICS region
Publication Date: 2024.12.10 IMPERVA INC
  • US12164897B2 patent drawing
  • US12164897B2 patent drawing
  • US12164897B2 patent drawing

AI summary

Embodiments of the present disclosure relate to systems and methods for installing a program within a CICS region without an antecedent program. A CICS region where the program is to be installed may detect an initiating event, the CICS region executing logical units of work that each corresponds to a task of a host operating system (OS). The initiating event may generate a first logical unit of work to intercept service calls made by the CICS region. In response to the first logical unit of work intercepting a first service call, control of execution of the first service call may be transitioned from the host OS to a CICS execution API. The CICS execution API may issue one or more API calls related to installation of the program, wherein the CICS execution API executes the one or more API calls as if they are part of the first service call.