Use this page to configure diagnostic trace service settings.
Supported configurations: You can only access this page when the server
is configured to use basic log and trace mode.
sptcfg
To view this administrative console page, click .
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
Trace Output
Specifies where trace output should be written. The trace
output can be written directly to an output file, or stored in memory
and written to a file on demand using the Dump button found on the
runtime page.
Different components can produce different amounts of trace output
per entry. Naming and security tracing, for example, produces a much
higher trace output than web container tracing. Consider the type
of data being collected when you configure your memory allocation
and output settings.
- None
- If this option is selected, the trace data is not logged or recorded
anywhere. All other handlers (including handlers registered by applications)
still have an opportunity to process these traces.
- Memory Buffer
- Specifies that the trace output should be written to an in-memory
circular buffer. If you select this option you must specify the following
parameters:
- Maximum Buffer Size
- Specifies the number of entries, in thousands, that can be cached
in the buffer. When this number is exceeded, older entries are overwritten
by new entries.
- File
- Specifies to write the trace output to a self-managing log file.
The self-managing log file writes messages to the file until the specified
maximum file size is reached. When the file reaches the specified
size, logging is temporarily suspended and the log file is closed
and renamed. The new name is based on the original name of the file,
plus a timestamp qualifier that indicates when the renaming occurred.
Once the renaming is complete, a new, empty log file with the original
name is reopened, and logging resumes. No messages are lost as a result
of the rollover, although a single message may be split across the
two files. If you select this option you must specify the following
parameters:
- Maximum File Size
- Specifies the maximum size, in megabytes, to which the output
file is allowed to grow. This attribute is only valid if the File
Size attribute is selected. When the file reaches this size, it is
rolled over as previously described.
- Maximum Number of Historical Files
- Specifies the maximum number of rolled over files to keep.
- File Name
- Specifies the name of the file to which the trace output is written.
Avoid trouble: This file cannot be shared
between servers. The server creates a file with a
.owner extension to help detect when two or more servers happen to be trying
to use the same file.
gotcha