Verbose logging message format

The following example shows a typical log message in verbose logging format. The text following the example explains the items in the message.

Verbose Logging Message Format
----------------------- 13:55:16 EDT  15 May 1997 -----------------------
CFG_DAEM Message 4097 - 132, Subcode: 1 - 1
Log category: PROBLEM   Cause Type: External
System: sna18
Process ID: 17908 (snacfgdae)

The initially active port could not be started when starting the node.
Port name = SDLCP0Cause:  The config daemon could not start the port while loading the node's
configuration. The node will be started, but the port will not be started.
Action:  Check for other logs which indicate why the port failed to start.
Check that the DLC has been started.

Verbose logging messages contain the following information:

Timestamp
The time and date the message was generated. If you are using central logging, the timestamp for each message is taken from the system clock on the computer where the message was generated. If the system clocks on different computers are not synchronized (because of clock inaccuracies or time zone differences), the messages in the central log file may appear out of sequence because they are added to the file in order of arrival at the central logger and not in order of their timestamps.

If your system includes Windows clients and you are using central logging, ensure that the TZ entry in the Windows Registry is set to indicate the correct time zone. If this is not set correctly, timestamps for logs from the Windows client may be incorrect. Refer to your Windows documentation for more information about the setting of TZ.

Component
The CS/AIX component (such as local node, link driver, or APPC library) that logged the message.
Message number
An identifier for the message. This identifier consists of two numbers.
Subcode
A unique identifier that indicates the point within CS/AIX at which the message was logged. This subcode is used only by CS/AIX support personnel.
Log category
The event category of the log message. Possible values are Problem, Exception, or Audit.
Cause type
The cause of the message. Possible values are:
Internal
Internal error in a CS/AIX component. Report errors of this type to CS/AIX support personnel.
System limit
An internal limiting value (for example, entries in a fixed-size table) in the CS/AIX software. There are very few instances when this type of log occurs.
External
A cause external to CS/AIX (such as a problem with communication link hardware) or in non-CS/AIX software (such as communication link drivers).
Resource
Resource shortage (for example, insufficient memory on the AIX computer).
User
User error (for example, invalid parameters supplied on the command line to a CS/AIX program).
SNA
SNA protocol violation by a remote system, or interoperability problem with another SNA implementation.
Config
Error in the CS/AIX configuration, or mismatch between the CS/AIX configuration and the remote system.
Audit
A normal event, reported for information only.
System name
The name of the computer where the condition that caused the message was detected.
Process ID and name
The AIX process ID (from the computer whose system name is shown) and the executable name of the process that logged the message. The process ID is shown only for user-space components. For a message logged by a Windows client, this parameter identifies the Windows task handle of the process.
Message text
Text describing the condition being logged. This field may include a number of variable parameters relating to this particular occurrence of the message. For example, a message reporting startup of an APPC session may include the names of the local and partner LUs and the mode they are using for this session.

This field can contain the return code from an operating system call. For a message logged by the AIX computer, it may be shown either as a symbolic name or as a numeric value. Check the numeric values in the /usr/include/sys/errno.h file on the computer where the error occurred to find the corresponding symbolic name. The symbolic names are listed in your operating system documentation.

For a message logged by a Windows client, refer to your Windows documentation for explanations of these return codes.

Message cause
Additional information about the cause of the condition being logged. This field may not be included if the message text contains all the required information. This field is generally not used when the cause type is Internal.
Message action
Recommended action as a result of the message. For audit messages, which provide accounting and progress information instead of reporting error conditions, this field is not included because no action is required.