Browse Prior Art Database

Events Set for Event Tracing in Distributed Object-Oriented Systems

IP.com Disclosure Number: IPCOM000114265D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 2 page(s) / 67K

Publishing Venue

IBM

Related People

Al-Karmi, AA: AUTHOR [+3]

Abstract

A mechanism for tracing, with fine granularity, a distributed transactional system is described. Further, none of the internal interaction details between transaction events are sacrificed.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Events Set for Event Tracing in Distributed Object-Oriented Systems

      A mechanism for tracing, with fine granularity, a distributed
transactional system is described.  Further, none of the internal
interaction details between transaction events are sacrificed.

      Interactions between objects are a very important aspect of
object models and particularly distributed objects.  However, the
tracing of events in the distributed environment is limited to RPCs
(Remote Procedure Calls) or Remote Object Invocation.  In Transaction
based systems (e.g., CICS* systems), such events are of minimal use.
The difficulty in tracing distributed transactions is the absence of
an event framework that can support coherent events as an entity.

      In solving this problem, use is made of events and event
triggers as a means of monitoring object interaction.  The notion of
"Events Set" and "Conditional Events Set" is introduced.

      Events Set (EVS) is a group of events that form an ordered set.
An EVS is completed when all of the events registered in that set
have been tracked.  Such events are not limited to a single object or
local objects but can be applied and related to multiple object as
well as local and remote objects.

      An EVS can also be "conditional".  A Conditional Events Set
(CEVS) is a set of ordered pairs of a condition and an event.  The
event pair is committed when the condition is met.  An example would
be the restriction on the number of threads in a process.  Such
restriction on the interaction between the "Process" Object and the
"Threads" Objects is a conditional event.

      An EVS can be user defined.  Since an EVS is a collection of
Event Objects, users can add to this collection all related event
objects.  When events are triggered, the collection object will mark
these objects.  On completion, if all objects are marked, the events
set will notify the collection processes of its completion.
Meanwhile, each event that is in the set, is tagged...