Browse Prior Art Database

Message Selection for a Message Management System for PC and PS/2

IP.com Disclosure Number: IPCOM000036446D
Original Publication Date: 1989-Sep-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 3 page(s) / 67K

Publishing Venue

IBM

Related People

D'Arielli, L: AUTHOR

Abstract

Disclosed is a design of Message Selection in a Message Management System for PC and PS/2 that reduces coding effort for the application developer and gives the user greater control over the treatment of messages. Any message may be directed to one or more devices (screen, printer) and/or files (log, activity), with the ability to exclude message elements (e.g., date and time) from being sent to any destination, or to exclude a destination altogether. The message ID contains codes for both class and severity, and the developer provides default selection criteria that the user can modify. These tables of selection criteria provide a simple yet highly flexible means of determining where each message will be sent, and in what form.

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

Page 1 of 3

Message Selection for a Message Management System for PC and PS/2

Disclosed is a design of Message Selection in a Message Management System for PC and PS/2 that reduces coding effort for the application developer and gives the user greater control over the treatment of messages. Any message may be directed to one or more devices (screen, printer) and/or files (log, activity), with the ability to exclude message elements (e.g., date and time) from being sent to any destination, or to exclude a destination altogether. The message ID contains codes for both class and severity, and the developer provides default selection criteria that the user can modify. These tables of selection criteria provide a simple yet highly flexible means of determining where each message will be sent, and in what form.

The key point is the structure of the message identifier "XXXcnnns", where "XXX" is the Software Product Acronym or the Software Major Component Acronym and "nnn" is the Message Number.

The message identifier includes two characters that describe the nature of the message, namely, the Message Class "c" and the Message Severity "s". This format imposes a discipline on the developer to categorize all the application messages into classes and severities. The message class is a way to subdivide all the application messages into categories that are meaningful to the end-user according to the type of their content. Examples of classes are I/O errors, transmission errors, etc. The message severity, on the other hand, classifies

(Image Omitted)

the message according to the level of intervention that the application requires from the user. Based on the combination of these two codes, a more granular and still simple filter grid can be built. This granularity is sufficient for most applications.

At the heart of the message handling system is a Message Customization File that contains, amongst other information, the Message Selection criteria: A fan-out vector, which determines what are the

possible destinations of messages - for example,

screen, printer, log file, activity file.

A filter matrix for each addressed device and file,

which determines which messages should be allowed

through, depending on the combination of class and

severity.

A format vector, which determines what components to

include in the message (for example, application module

name, message ID, message text and its imbedded

variables, date and time). Fig. 1 shows, in tabular

form,...