Browse Prior Art Database

A method to dynamically route user requests in a distributed system, based on detected maintenance levels of components within the system

IP.com Disclosure Number: IPCOM000236079D
Publication Date: 2014-Apr-04
Document File: 4 page(s) / 159K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method to dynamically route user requests in a distributed system, based on detected maintenance levels of components within the system

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 01 of 4

A method to dynamically route user requests in a distributed system, based on detected maintenance levels of components within the system

A distributed processing environment may not be homogeneous with regard to the software maintenance applied to its constituent components. Also, given user requests to a transaction processing system, such as IBM CICS Transaction Server, the API/SPI calls that will be made by the request can be anticipated based on the requested transaction. This disclosure describes a method whereby user requests can be can be routed to the components in a distributed system which have the appropriate level of maintenance applied.

    This solution ensures that the API/SPI being used will perform to the appropriate service levels as the calls will be made to systems with appropriate maintenance applied.

    A product such as IBM CICS Deployment Assistant creates a model of CICS regions in its target Sysplex. Such a model can be augmented to include information regarding the levels of service applied to each of the regions in the model. This information can be used to predict what maintenance, if any, is required to enable any particular user request to be executed without problems.

    In addition, the information can be used to re-route requests away from systems that could encounter known errors due to service only having been applied to certain running systems as is so often inevitable in 24x7 environments with carefully controlled maintenance schedules. This increases the availability of the system and reduces outages of the system due to required system updates.

    It should be noted that while this description is CICS-centric, this approach could be applied (with appropriate small modifications) to other complex systems based on the IBM z/OS operating systems, and even to systems based on architectures other than z/OS such as Windows and Linux-based distributed applications.

    This invention required the generation of 4 tables how theses are created is detailed in the steps below. In the figures the tables are labelled A, B, C and D, the relations they represent are summarized here:

Table A - (Region

PTF)

    Cross reference of running CICS regions against their applied service level Table B - (Txn/Program

API/SPI )

Cross reference of CICS transactions and programs against the API and SPI calls used in those programs
Table C - (API/SPI

Module)

    Cross reference of CICS API and SPI to the CICS modules which could be required during an invocation of those API/SPI calls
Table D - (Module

PTF)

    Cross reference of CICS...