Browse Prior Art Database

Managing Messages

IP.com Disclosure Number: IPCOM000103912D
Original Publication Date: 1993-Feb-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 4 page(s) / 122K

Publishing Venue

IBM

Related People

Cunningham, G: AUTHOR [+5]

Abstract

A method is disclosed for keeping operating system-generated and application-generated message outputs consistent and ensuring timely review of message information.

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

Managing Messages

      A method is disclosed for keeping operating system-generated
and application-generated message outputs consistent and ensuring
timely review of message information.

      Currently, for most operating systems and applications, message
information is maintained and managed in a variety of places:
message issuing mechanisms with message text in modules; message text
and explanations in book files; possibly message routing and
descriptor codes in separate book files; National Language Support
(NLS) message skeletons in separate files or data sets; message
prolog information in modules; and, message program temporary fix
(PTF) cover letter information.  As messages are updated, changed,
and deleted throughout a release cycle, messages are not consistently
maintained in all places, thus introducing numerous errors into the
external customer publications, internal publications, and message
skeletons.  The method disclosed ensures timely review of and
consistency among message outputs and elimination of errors in
external customer publications.  Fig. 1 illustrates the method of
message management suggested.

The message management method is defined as follows:

o   All message data resides in a single database, and users request
    the various required outputs through a user interface that
    communicates with the database.  The user requests other
    message-related functions through the interface, thus ensuring
    that all people who create messages follow a common process.

o   The interface provided for creating and editing messages ensures
    that messages comply with the corporate standard.

o   The interface provided for creating and editing messages enforces
    the following message creation, change, and deletion process:

    For a new or changed message:

    1.  A defect correction process or the new development process
        triggers the creation of the message.  The defect correction
        and new development processes will be directly tied to the
        interface provided for managing messages.

    2.  The developer obtains a new message identifier.

    3.  For messages, the developer inputs the message text into the
        database.  The message management method validates that the
        message text does not violate the corporate standard.  Once
        entered, a note is sent to a writer in the Information
        Development (ID) department, indicating that the message text
        needs to be reviewed.

    4.  The message management method coordinates review of messages
        among developers, ID, NLS coordinators, test, automated
        operations package owners, and other interested parties
        through various views of messages, such as the book
        (formatted), console, prolog, or message skeleton view.  The
        review process takes...