Logging streams and expected output

Investigating the logging and tracing output for the application server is an excellent way to observe performance, diagnose problems, and gain a general understanding of how the application server is working within your environment. The expected output locations for logging and trace information can be different depending on the operating system on which the application server is running.

When the application server is installed on z/OS, the logging and output streams are directed as follows:
Table 1. Log and trace output for z/OS
Log or trace stream Expected output
Tracing (both native trace and Java tracing) SYSPRINT
Avoid trouble Avoid trouble: Trace information, which includes events at the Fine, Finer and Finest levels, will be written only to this output. If you do not enable diagnostic trace, setting the log detail level to Fine, Finer, or Finest does not effect the logged data.gotcha
Tracing level equal to the Audit level Transformed into write-to-operator (WTO) output to the hard copy logging stream
Tracing level equal to or above the Detail level SYSOUT or your configured error stream
Messages, including native messages and most trace messages SYSOUT or your configured error stream
System.out SYSPRINT
System.err SYSPRINT
When considering the direction of log and trace streams, keep in mind the following acronyms and abbreviations:
cerr
C or C++ error steam
cout
C or C++ output steam
DD
Data Description statements
HFS
HTTP File Server
JCL
Java Control Language
JES
Java error stream
MVS
Multiple Virtual Storage
WTO
Write-to-operator
WTOR
Write-to-operator with reply



Related concepts
Java logging
Related tasks
Adding logging and tracing to your application
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=cprf_logging
File name: cprf_logging.html