Message format

There are differences among the formats of error messages written to the AIX® error log, or Linux®, Windows, or Solaris system logs.

Table 1 describes the message formats on AIX, Linux, Windows, and Solaris system platforms.
Table 1. Error message formats in the AIX error log, and Linux, Windows, and Solaris system logs
System platform Error message format sample
AIX
LABEL:          TS_LOC_DOWN_ST
IDENTIFIER:     173C787F  
Date/Time:      Wed May 20 23: 34:55 EDT
Sequence Number: 5434
Machine Id:      000123456A00
Node Id:         c684n09
Class:           S
Type:            INFO
Resource Name:   cthats  

Description
Possible malfunction on local adapter  ⋮
Linux
May 20 23:34:55 c117f1n1 cthats[10062]: (Recorded using  
libct_ffdc.a cv 2):::Error ID:  
824....m/6V2/rEl176ba20...................:::Reference ID:
:::Template ID: 0:::Details File:  :::Location:  
rsct,nim_control.C,1.39.1.1,4147              
:::TS_LOC_DOWN_ST Possible malfunction on local adapter  
...
Windows
Jun 28 08:41:11 rsctvm2 RMCdaemon
[26883]: (Recorded using
libct_ffdc.a cv 2):::Error ID:  
824....bluU4/B7B0..............
...........:::Reference ID:  ::
:Template ID: 0:::Details File:
  :::Location: RSCT,rmcd.c,1.51,
209       :::RMCD_INFO_0_ST  
The daemon is started.
Solaris
Mar 10 01:09:03 e106e335n09.ppd.pok.ibm.com ConfigRM[3398]: [ID 489967 daemon.no
tice] (Recorded using libct_ffdc.a cv 2):::Error ID: :::Reference ID:  :::Templa
te ID: 0:::Details File:  :::Location: RSCT,ConfigRMDaemon.C,1.12,176
     :::CONFIGRM_STOPPED_ST IBM.ConfigRM daemon has been stopped.
Table 2 further describes the message formats shown in Table 1
Table 2. Error message format descriptions of the AIX error log , and Linux, Windows, and Solaris system logs
AIX error log Linux system log Windows system log Solaris system log
The LABEL field contains a unique string identifying the error. In this manual, you can use the label to look up information on the error. The Resource Name field indicates the specific RSCT subsystem that generated the error. The error entry ends with a description of the error.

For more information on any of the other fields of the error log entry, see the online man page for the errupdate command.

Individual fields within the error record are separated by three colons (:::).

The first field of the error record contains a timestamp followed by the name of the node on which the error occurred, followed by the resource name. The resource name indicates the specific RSCT subsystem that generated the error.

The Location field provides information about the code that detected and recorded the incident.

The description of the incident follows the last set of colon separators. For most RSCT subsystems, the description will start with a label (in the preceding example, the label is TS_LOC_DOWN_ST). In this manual, you can use the label to look up information on the error.

Individual fields within the error record are separated by three colons (:::).

The first field of the error record contains a timestamp followed by the name of the node on which the error occurred, followed by the resource name. The resource name indicates the specific RSCT subsystem that generated the error.

The Location field provides information about the code that detected and recorded the incident.

The description of the incident follows the last set of colon separators. For most RSCT subsystems, the description will start with a label (in the preceding example, the label is RMCD_INFO_0_ST). In this manual, you can use the label to look up information on the error.

Individual fields within the error record are separated by three colons (:::).

The first field of the error record contains a timestamp followed by the name of the node on which the error occurred, followed by the resource name. The resource name indicates the specific RSCT subsystem that generated the error.

The Location field provides information about the code that detected and recorded the incident.

The description of the incident follows the last set of colon separators. For most RSCT subsystems, the description will start with a label (in the preceding example, the label is RMCD_INFO_0_ST). In this manual, you can use the label to look up information on the error.