IMS Batch Application Resource Suspension Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
IMS batch application programs face downtime issues when maintaining shared resources, as they must be terminated for database maintenance, leading to undesirable outages and operational risks, while maintenance without termination results in suboptimal performance.
Innovation Solution
Enabling IMS batch application programs to temporarily suspend and resume access to shared IMS resources without termination, using a separate Task Control Block and 'front-ending' the IMS Language Interface routine to manage resource access externally, allowing continuous operation and maintenance without restarting the applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IMS batch application programs are terminated to release shared IMS resources for maintenance, then resource maintenance can be performed, but application availability is lost and operational risks increase
Solution Approach 1:
The system separates the batch application program execution from the IMS resource access by creating a suspension mechanism. The application program continues running in the batch region while IMS resources are temporarily suspended and allocated to maintenance tasks, resolving the contradiction between maintaining application availability and enabling resource maintenance.
Solution Approach 2:
An intermediary suspension mechanism is introduced between the batch application program and the IMS resources. This intermediary allows the system to decouple the application execution from resource access, enabling resources to be released for maintenance while applications continue running, thus maintaining availability while enabling maintenance.
2Reliability
If IMS batch application programs continue running during resource maintenance, then application availability is maintained, but resource maintenance cannot be performed effectively
Solution Approach 1:
The system introduces dynamic control over resource allocation by allowing temporary suspension and resumption of IMS resource access. Batch application programs can dynamically suspend access when maintenance is needed and resume when complete, enabling both continuous availability and effective maintenance without permanent termination.
Solution Approach 2:
The suspension and resumption of IMS resource access occurs periodically based on maintenance needs rather than requiring permanent termination. This periodic action allows maintenance tasks to be performed at scheduled intervals while maintaining continuous application availability, resolving the productivity-availability contradiction.
3Ease of manufacture
If batch application programs are restarted after termination, then resource access can be restored, but operational risks increase and additional resources are consumed
Solution Approach 1:
The batch application program maintains its own execution context and state within the batch region, serving itself by continuing to run without termination. When IMS resources are suspended, the application simply waits in a suspended state rather than being terminated and restarted, eliminating the operational risks and resource consumption associated with program restart.
Data Source
AI summary
The present invention includes aspects pertaining to enabling an IMS batch application program to temporarily release its access to IMS resources that it shares with an IMS database management system or other non-IMS system agent, without terminating the application program. The present invention identifies when the batch application program issues a call that generate a sync point, and disconnects the program's connection to the IMS resources. The batch application program retains access to any independently obtained non-IMS resources when the program is disconnected from the IMS resources. The IMS database management system or other non-IMS system agent has temporary exclusive access to the IMS resources after the batch application program connection is disconnected. After such temporary exclusive access is complete, the batch application program's connection to the IMS resources is reestablished, and the batch application receives a response to its original call that generated a sync point. In another embodiment of the present invention, a plurality of IMS batch application programs temporarily release their access to IMS resources. In this embodiment, the IMS database management system or other non-IMS system agent obtains temporary exclusive access to the IMS resources after all of said plurality of batch application program connections to IMS resources are disconnected.