![[z/OS]](../images/ngzos.gif)
System performance when logging messages and trace data
Using message logging and trace data can affect system performance depending on your system configuration.
You can select the amount and types of trace data to be collected, which provides you with the ability to either run your application with minimal tracing when performance is a priority, or run your application with detailed tracing when you need to recreate a problem and collect additional diagnostic information.
The
error log stream, the CTRACE data set for WebSphere® Application Server for z/OS®, and the master console are
primarily intended for monitoring or recording diagnostic data for
system components and critical applications. Depending on your installation's
configuration, directing application messages and data to these resources
might have an adverse affect on system performance. For example, if
you send application data to the CTRACE data set, trace entries in
that data set might wrap more quickly, which means you might lose
some critical diagnostic data because the system writes new entries
over existing ones when wrapping occurs. Use this logging support
judiciously.
Note: You can only use WebSphere Application Server for z/OS support for logging messages
and trace data for Java™ applications, not for Java applets.