Log and trace settings

Use this page to view and configure logging and trace settings for the server.

To view this administrative console page, click:
[z/OS] Note: You can configure tracing from the MVS console using the modify command.

Diagnostic Trace

The diagnostic trace configuration settings for a server process determine the initial trace state for a server process. The configuration settings are read at server startup and used to configure the trace service. You can also change many of the trace service properties or settings while the server process is running.

Java virtual machine (JVM) Logs

[AIX HP-UX Linux Solaris Windows] [iSeries]

The JVM logs are created by redirecting the System.out and System.err streams of the JVM to independent log files. WebSphere® Application Server writes formatted messages to the System.out stream. In addition, applications and other code can write to these streams using the print() and println() methods defined by the streams.

Process Logs

[AIX HP-UX Linux Solaris Windows] [iSeries]

WebSphere Application Server processes contain two output streams that are accessible to native code running in the process. These streams are the stdout and stderr streams. Native code, including Java virtual machines (JVM), might write data to these process streams. In addition, JVM provided System.out and System.err streams can be configured to write their data to these streams also.

IBM Service Logs

[AIX HP-UX Linux Solaris Windows] [iSeries]

The IBM service log contains both the WebSphere Application Server messages that are written to the System.out stream and some special messages that contain extended service information that is normally not of interest, but can be important when analyzing problems. There is one service log for all WebSphere Application Server JVMs on a node, including all application servers. The IBM Service log is maintained in a binary format and requires a special tool to view. This viewer, the Log and Trace Analyzer, provides additional diagnostic capabilities. In addition, the binary format provides capabilities that are utilized by IBM support organizations.

Change Log Level Details

Enter a log detail level that specifies the components, packages, or groups to trace. The log detail level string must conform to the specific grammar described in this topic. You can enter the log detail level string directly, or generate it using the graphical trace interface.




Related tasks
Diagnosing problems with message logs
Related reference
[z/OS] Modify command
[z/OS] Example: Establishing a general level of trace
[z/OS] Example: Setting basic and detailed trace levels
[z/OS] Example: Setting specific trace points
[z/OS] Example: Excluding specific trace points
[z/OS] Example: Resetting to the initial trace settings
[z/OS] Example: Turning off tracing
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=logsandtrace_description
File name: utrb_logtrace.html