HP-UX SNAplus2 Diagnostics Guide

Using Logging and Tracing
Controlling Logging Using Command-Line Administration Program
Chapter 370
Choosing the Format of Logs
You control the amount of detail recorded in logs by choosing one of the
following logging formats:
Verbose logging
Each message contains the message number,
originating component, type of message, text of the
message, the cause of the condition leading to the
message, and any recommended action.
Succinct logging
Each message contains only an abbreviated version of
the header information (message number, originating
component, and message type) and the text of the
message. You can use the snaphelp command-line
utility to obtain the cause and action information for a
particular message number (see “Using snaphelp for
Succinct Logging Messages”).
The default is succinct logging. You can specify verbose logging for audit
messages, for error messages (problem and exception), or for both
message types by using the set_log_type commandor snapadmin
set_global_log_type command. If you are using central logging, the
choice of succinct or verbose logging is determined by the settings on the
server acting as the central logger, so all messages of the same type
(audit or error) are written to the file in the same format.
When using succinct logging, a few messages from the 3270 emulation
program, RJE workstation program, and API components may still be
written to the log file in verbose format. This generally occurs when
SNAplus2 is terminating or experiencing certain error conditions; in
these cases, the component cannot obtain information about the node's
configuration and cannot determine the log format to use.
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.
Example 3-1 Verbose Logging Message Format