Browse Prior Art Database

Method for Table-Driven Dynamic Event Notification (Alerts)

IP.com Disclosure Number: IPCOM000035707D
Original Publication Date: 1989-Aug-01
Included in the Prior Art Database: 2005-Jan-28
Document File: 7 page(s) / 211K

Publishing Venue

IBM

Related People

Bucknell, LM: AUTHOR [+4]

Abstract

The purpose of this invention is to provide a means to report problem or other significant events to a system remote from the one where the the problem or event occurred using an architecture that defines many discrete data elements (the Generic Alert Architecture). Attempting to pre-define and code all possible combinations and permutations is not a realistic solution especially since many of them may never be used within the life of a product. (Image Omitted)

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

Page 1 of 7

Method for Table-Driven Dynamic Event Notification (Alerts)

The purpose of this invention is to provide a means to report problem or other significant events to a system remote from the one where the the problem or event occurred using an architecture that defines many discrete data elements (the Generic Alert Architecture). Attempting to pre-define and code all possible combinations and permutations is not a realistic solution especially since many of them may never be used within the life of a product.

(Image Omitted)

A key secondary requirement was to provide a solution that would allow updating of the data used to create an alert with minimal effort.

This invention provides the ability to dynamically generate an event notification, called an "Alert", based on the data available at either the time of the event or after additional data about the event has been developed, for example, by running problem analysis procedures.

It also provides a solution for resolving differences when multiple data records with different data are provided for the same event but only one instance of the data is allowed.

Some of the terms used in this article are defined following: ACT-Alert code table, a table containing data used to generate alerts.

(Image Omitted)

ALERT-A construct used to provide notification of an event and data about the event to a location remote from the location where the event occurred. ALRGEN- The component that generates an alert. ELID-Error log identification, used to identify a specific entry in the error log. FRU-A Field Replaceable Unit, used to indicate any cause of an event, such as a hardware or software component and also causes external to a system, such as electrical power, temperature, or user procedures.

(Image Omitted)

PAR-Problem analysis and resolution procedures. PARABLE PROBLEM-A problem for which problem analysis and resolution procedures are provided in the product. PARABLE MESSAGE-A message about a problem for which problem analysis and resolution procedures are available.

REFERENCE CODE-A Reference code is the 4-digit encoded name of a detected condition. RCT-Reference code table, a table containing both data used for problem analysis and data used to generate alerts. VPD-Vital product data, data about a product, such as type and serial number for a hardware product or a program product ID for software.

(Image Omitted)

1

Page 2 of 7

For more information about alerts, refer to Systems Network Architecture, Format and Protocol Manual: Management Services IBM form number SC0- 3346.

Prior to this time, systems and products that sent alerts were primarily those that used the old alert architecture which required stored screens at the alert receiver (focal point). Only those alerts that had screens defined and stored at the host system could be sent except for some based on included text only.

Currently, other products that send alerts using the new Generic Alert Architecture do so by defining a limited numb...