Messages and error codes

The system messages can be viewed in the following ways:
  1. In real time, as on the operator console.
  2. In an offline-type mode, as in the logging files that are written to disk.

Console message format

For console-based messages, the format is
hh:mm:ss  aaaaaaaaaaaaaa > iiinnnnns: ttttttttttttttt...tttttttttttttt
The following list shows the values that the patterns in the message format represent.
hh:mm:ss
This pattern represents the time that the message was issued.
aaaaaaaaaaaaaa
This pattern represents the name of the component that issued the message.
iii
This pattern represents the three-character message identifier.
nnnnn
This pattern represents a unique message number for that component.
s
This pattern represents the message severity level.
ttttttttt...ttttttttt
This pattern represents the message text.
The following text is an example of a console message
12:45:20  Master  >  0010I: Transaction Server is starting

Log message format

For log files, the message is in XML format. The following text is an example of a log message.

<record>
   <date>2004-01-13T15:27:39</date>
   <millis>1074025659577</millis>
   <sequence>1</sequence>
   <logger>Transaction Server</logger>
   <level>INFO</level>
   <class>Logging manager</class>
   <method>?</method>
   <thread>10</thread>
   <message>LGM00030I: Console message level has been changed to ALL</message>
</record>
The following list describes the information that is contained in the XML elements.
record
This element defines the beginning of a log record.
date
This element contains the date and time that the message was issued.
millis
This element contains the number of milliseconds since midnight on 1 January 1970.
sequence
This element contains a numeric sequence number that identifies the position of the message.
logger
This element contains the name of the component that logged the message.
level
This element contains the value of the message level for the message.
class
This element contains the name of the Java™ class that logged the message.
method
This element contains the name of the Java method that logged the message.
thread
This element contains the thread ID of the thread that logged the message.
message
This element contains the log message.

Message severity

The following levels of message severity can accompany a message.
S
Severe errors that are issued as the result of a serious error
W
Warning messages that indicate a problem. Typically, the system recovers and continues to function correctly.
I
Information messages
K
Tracking messages
L
Information messages
T
Trace messages
E
Error messages, but less severe than "S"
D
Debug messages
F
Debug messages
Notes:
  1. All messages are written to the system logs.
  2. If the console message level is set to INFO, only messages with a severity level of I, W, or S are sent to the console.
  3. If the console message level is set to ALL, all messages are sent to the console.
  4. Trace messages are only issued when the system trace option was set to true.

Finding a message

To make it easier to find a message, all messages are alphabetized by the letters that designate their components.

FTM components can log messages from other software that they use, such as CWW messages from IBM® WebSphere® Liberty. If an error message cannot be found in these lists of messages and error codes, look for the message in the documentation for the other software products.