Browse Prior Art Database

Handling DCE Insufficient Memory Events

IP.com Disclosure Number: IPCOM000014577D
Original Publication Date: 1999-Dec-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 1 page(s) / 37K

Publishing Venue

IBM

Related People

Woodrow Arkeketa: AUTHOR [+3]

Abstract

With the addition of the *Tivoli Distributed Computing Environment (DCE) Serviceability Event Adapter and the potential occurrence of about 100 different DCE Serviceability messages relating to memory allocation, it was felt that more emphasis should be placed on these events. This was primarily because any one or all of these events could be easily missed at the Tivoli Event Console in among all the other events.

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

Page 1 of 1

Handling DCE Insufficient Memory Events

With the addition of the *Tivoli Distributed Computing Environment (DCE) Serviceability Event Adapter and the potential occurrence of about 100 different DCE Serviceability messages relating to memory allocation, it was felt that more emphasis should be placed on these events. This was primarily because any one or all of these events could be easily missed at the Tivoli Event Console in among all the other events.

This disclosure describes the actions taken to make the occurrence of this type of event be more visible. This was done by generating a new event, the DCEInsufficientMemory event, for each occurrence of a DCE related memory allocation failure from a specific DCE host. This in itself meant that the user could see by its class name and fatal severity that something was beginning to happen on that DCE host with regard to memory allocation. The remainder of the handling of the event deals with duplicate event processing and maintaining an audit trail of all of the DCE Serviceability messages (message identifier and message text) that resulted in the event or a duplicate of the event. In addition to the audit trail of message information, the date of the last duplicate is maintained. This allows an administrator to look at the detailed event output and determine the time span over which the DCEInsufficientMemory event was in effect.

*Tivoli Tivoli is a trademark of Tivoli Systems Inc.

1