(zos)

Logging messages and trace data for Java server applications

By using the WAS for z/OS support for logging application messages and trace data, we can improve the reliability, availability, and serviceability of any Java application that runs in a WAS for z/OS server.

Through this support, the Java application's messages can appear on the MVS™ master console, in the error log stream, or in the component trace (CTRACE) data set for WebSphere Application Server for z/OS. Your application's trace entries can appear in the same CTRACE data set.

1. Determine where to issue the log messages. Read Message location best practices for tips on which tools to use.

2. Configure logging in the MVS master console, the error log stream, or the CTRACE data set.

Subtopics

• (zos) Message location best practices
  Use this information for configuring messaging locations.

• (zos) System performance when logging messages and trace data
  Using message logging and trace data can affect system performance depending on the system configuration.

• (zos) Issuing application messages in the MVS master console
  With the WAS for z/OS reliability, availability, and serviceability support for Java (JRas) framework, we can issue messages from the Java application to the MVS master console. We might want to issue messages to the master console to report serious error conditions for mission-critical applications, or to trigger automation packages.