Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Application/Subsystem Conversation Interface Using Synchronization Timers

IP.com Disclosure Number: IPCOM000059755D
Original Publication Date: 1986-Jan-01
Included in the Prior Art Database: 2005-Mar-08
Document File: 2 page(s) / 53K

Publishing Venue

IBM

Related People

Shorter, DU: AUTHOR

Abstract

This article describes a method that will allow a set of applications or subsystems to converse across address space boundaries of the MVS operating system, regardless of protect key or operating priority. The conversation may occur on a one-to-one or one-to-many basis. It eliminates the need for the higher overhead cross-memory services in many situations. A need exists to interchange information between separate applications. In many cases, there is no requirement for an immediate information request-wait-answer type of protocol. An example where this would be true is if one of the applications was a monitor that reported on the performance status of other applications running in the same computer. The information desired is only time dependent within a particular time interval. That interval could be minutes.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Application/Subsystem Conversation Interface Using Synchronization Timers

This article describes a method that will allow a set of applications or subsystems to converse across address space boundaries of the MVS operating system, regardless of protect key or operating priority. The conversation may occur on a one-to-one or one-to-many basis. It eliminates the need for the higher overhead cross-memory services in many situations. A need exists to interchange information between separate applications. In many cases, there is no requirement for an immediate information request-wait-answer type of protocol. An example where this would be true is if one of the applications was a monitor that reported on the performance status of other applications running in the same computer. The information desired is only time dependent within a particular time interval. That interval could be minutes. Through the process described in this article, less computer resources could be used to accomplish the information exchange while minimizing the impact on the designed work of the applications. The point of contact between applications is storage areas that may be accessed by the participating entities. The first level is a control block anchor point located in the MVS nucleus. It is used to provide addressability to control blocks located in the MVS common systems area (CSA). Through the use of these common areas, multiple applications can access the same storage locations. This method requires an environment controller whose purpose is to construct and initialize the necessary control blocks and set the anchor point in the nucleus. It can run in a separate address space or be part of one of the applications. Following is a description of the method by an example: Application (APPL) 4 requires information from APPL 1. The process through which the information is requested and provided is described as a sequential series of events. Refer to Fig. 1 for the storage map used in the following dis...