Browse Prior Art Database

Event Completion and Event Feedback Separation

IP.com Disclosure Number: IPCOM000079613D
Original Publication Date: 1973-Aug-01
Included in the Prior Art Database: 2005-Feb-26
Document File: 2 page(s) / 29K

Publishing Venue

IBM

Related People

Boggs, JK: AUTHOR [+3]

Abstract

Event completion and event feedback have traditionally been bound together in an event control block (ECS). This causes complexity and confusion when the operating system definition of an asynchronous process which can WAIT on an event, differs from the definition of an asynchronous process in a component of the operating system.

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 100% of the total text.

Page 1 of 2

Event Completion and Event Feedback Separation

Event completion and event feedback have traditionally been bound together in an event control block (ECS). This causes complexity and confusion when the operating system definition of an asynchronous process which can WAIT on an event, differs from the definition of an asynchronous process in a component of the operating system.

In OS/360, an ECB represents a single event. When WAIT is performed, then the address of this ECB is presented to the system and the task WAIT's. If the task has within its logic internal definition of several asynchronous processes, it becomes necessary to have an ECB defined for at least each process and a multiple WAIT list upon which to wait. This technique is called subdispatching. This approach has been used for example by telecommunications access method (TCAM). However, the problem exists that either the multiple wait list becomes quite long or it is dynamically built using complex logic.

The solution to the problem stated is to define an event and its feedback to be separate. A new interface has been created wherein when requested, both the address of the ECB and the address of the feedback area are presented. As an example which has been implemented, Page Load may be issued many times and each completion kept distinct, yet with only one ECB defined and used for WAIT.

1

Page 2 of 2

2

[This page contains 2 pictures or other non-text objects]