User-defined message explanations

If one of your applications writes a message to the SYSLOG, and the application subsequently abends, then Fault Analyzer looks through IDIHUSRM, to see if it can find a message associated with the identifier of the issued message. If it finds a match, then Fault Analyzer is able to include the message explanation in the analysis report.

The message explanation header record in IDIHUSRM has the following format:

Figure 1. Syntax

where

message_identifier

A code identifying the message. This code can be any combination of numbers and letters. It is not case-sensitive. For example:

MYMESSAGE
m103a
dbg303

are all valid message identifiers.

For the purpose of providing message explanations, Fault Analyzer treats all characters from the start of any message, up until the first blank character, as constituting the message identifier being searched for.

Any plus signs (+) that MVS™ might add to the start of messages when these are being displayed are not considered part of the message identifier. If these are included in the IDIHUSRM member, then they are ignored.

Note that :msg. must begin in column 1.

The lines of the message following the header record are transferred directly as you type them in. So if you include leading spaces in the explanation, then Fault Analyzer includes the leading spaces when it prints the message.

In the following example, two messages are defined:

:msg.payrollmsg1
Processing of accumulated leave about to commence.
 - If processing fails after this point,
   check for negative accumulations.
:msg.payrollmsg2
Processing of accumulated leave completed.

When using the LOOKUP command, user-defined messages appear in the "Messages" main category, under the subcategory name consisting of the first 3 characters of the message ID.