IBM Storage Protect Snapshot message format

Messages consist of the following elements:

A three-letter prefix.
A numeric message identifier.
A one-letter severity code, also called the message type.
Message text that is displayed on screen and written to message logs.
Explanation, System Action, and User Response texts. These texts elaborate on the message text, and are accessible only in documentation.

The image presents a typical message. The callouts on the right of the image identify each element of the message.

The severity codes give an indication of the severity of the issue that generated the message. The severity codes and their meanings are as follows:


Code	Severity	Meaning
S	Severe	The product or a product function cannot continue. User response is required.
E	Error	An error is encountered during processing. Processing might stop. User response might be required.
W	Warning	Processing continues, but problems might occur later as a result of the warning.
I	Information	Processing continues. User response is not necessary.

Message variables in the message text appear in italics.

On IBM Storage® Protect Snapshot for UNIX™ and Linux™ systems and in IBM Storage Protect Snapshot for VMware environments, some logs append an extra prefix to the message.

In the detailed log, messages are prefixed with a timestamp and a session ID. The session ID can help you determine whether the message was produced from the application or the device. It can help you distinguish different application and device nodes. For DB2® DPF databases, the session ID can help you to determine which DB2 node or which storage cluster was responsible for producing the message.

The following example contains a prefix:


15:41:07 (626) FMM8300I tsmACSPartition() returned with code 18.

In the summary log, there is an extra prefix that indicates what operation caused the request.

Here is an example of the prefix in the summary log:


DB  00:16:48 (92e) FMM1510I New connection received.