Browse Prior Art Database

Imbedding Messages within Messages Disclosure Number: IPCOM000114567D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 4 page(s) / 115K

Publishing Venue


Related People

Igel, SM: AUTHOR [+2]


A method for constructing one complete and specific message by chaining smaller messages together is disclosed.

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

Imbedding Messages within Messages

      A method for constructing one complete and specific message by
chaining smaller messages together is disclosed.

      Today messages are defined to represent all possible events.
For example: if one event has 10 possible causes and each cause has
10 possible recovery actions, 100 messages would need to be defined
to represent the possible combinations.

      By modifying the use of the last variable, which is used to
represent a variable length field, defined for each message complete
messages can be constructed from smaller pieces and be made to fit
specific circumstances.  With this capability, a second system
message can be retrieved and formatted into character format.  The
raw character data can then be appended to the variable data of the
first system message.  To the AS/400* operating system, the merged
message is just a system message with new variable data.  This
process can be continued indefinitely, allowing many messages to be
imbedded within each other.

      This implementation does not preclude the use of other message
storing schemes.  Each message can still be compressed, and broken
into smaller tokens which represent common phrases or words.  The
current use of replacement text within the message test will continue
for each message.  The additional feature is the existing replacement
text can now point to another complete message.

Conceptually this can be represented as shown in the Figure.

      This allows the system to display a message which is specific
to the current events, without requiring the complete message to be
built ahead of time.

A service message will be used to demonstrate the advantages.
  MsgId ONE
  Message . . . . :  Line &23 failed.
  Cause   . . . . :  The following may have caused the problem:
                      -The input output adapter &26
                      -The Licensed Internal code
  Recovery  . . . :  Vary off the line and then vary on the line
                      using reset(*yes).  If the problem continues
                      press F14 to work with the problem.

      Without using the enhanced message handling scheme, even though
the Message part of MsgId ONE did not need to change, a complete new
message had to be created to represent different Causes and another
message defined when different Recoveries were needed.  By the time
the message was ready to be displayed, some of the potential causes
may have been eliminated and would no longer need to be displayed.
To accurately display the information a message needed to be defined
for every possible combination of Message, Cause, and Recovery text.

      By using message concatenation, MsgId ONE can be broke into 3
or more parts.  Replacing one part with a different message id will
not require a message which contains the other parts.  The code which