HP-UX SNAplus2 R7 Administration Guide

Managing SNAplus2 Client/Server Systems
Managing Win16 Clients
Specifies whether to use succinct logging or verbose logging in the error log file. This setting applies to both
exception logs and problem logs. You can specify either of the following values:
YES
Use succinct logging: each message in the log file contains a summary of the message header
information (such as the message number and log type) and the message text string and parameters. To
obtain more details of the cause of the log and any action required, you can use the
snaphelp utility
on a computer running HP-UX.
NO
Use verbose logging: each message in the log file includes a full listing of the message header
information, the message text string and parameters, and additional information on the cause of the
log and any action required.
This parameter is optional. If it is not specified, the default is taken from the previous
set_global_log_type command issued to the master server (or set using the Motif adminis-
tration program). The initial default, before any set_global_log_type command has been issued, is to
use succinct logging.
If you are using central logging, the choice of succinct or verbose logging for messages from all computers
is determined by the setting of this parameter on the server acting as the central logger; this setting may
either be from the set_global_log_type command, or from a set_log_type command issued to
that server to override the default.
succinct_audits
Specifies whether to use succinct logging or verbose logging in the audit log file. The permitted values and
their meanings are the same as for the succinct_errors parameter.
[API_tracing]
The [API_tracing] section of the file specifies API tracing options for applications running on the client. For
more information about tracing, refer to HP-UX SNAplus2 Diagnostics Guide. The tracing options are specified as
follows:
file1
The full path name of the trace file, or of the first trace file if tracing is to two files (see the description of
the file2 parameter).
This parameter is required if you want to enable API tracing.
file2
The full path name of the second trace file. This parameter is optional; to indicate that tracing is to one file
instead of two files, do not include this line.
If both file1 and file2 are specified, tracing is to two files. When the first file reaches the size specified by
the flip_size parameter, the second file is cleared, and tracing continues to the second file. When this file
then reaches the size specified by flip_size, the first file is cleared, and tracing continues to the first file. This
ensures that tracing can continue for long periods without using excessive disk space; the maximum space
required is approximately twice the value of the flip_size parameter.
flip_size
The maximum size of the trace file. If two file names are specified, tracing switches between the two files
when the current file reaches this size. If only one file name is specified, this parameter is ignored; the file
size is not limited.
This parameter is optional. If it is not specified, the default is 100000 (bytes).
truncation_length
The maximum length, in bytes, of the information written to the trace file for each message. If a message is
longer than this, SNAplus2 writes only the start of the message to the trace file, and discards the data beyond
165