WebSphere traces can be extremely helpful in detecting and diagnosing problems. By properly setting trace options, you can capture the information needed to detect problems without significant performance overhead.
You should check your WebSphere for z/OS tracing options to ensure that ras_trace_defaultTracingLevel=0 or 1, and that ras_trace_basic and ras_trace_detail are not set.
How to view or set: Use the WebSphere administrative console:
ras_trace_defaultTracingLevel=1 will write exceptions to the trace log as well as to the ERROR log.
If you are tracing to sysprint with ras_trace_defaultTracingLevel=3, you may experience an almost 100% throughput degradation. If you are tracing to CTRACE, however, you may only experience a 15% degradation in throughput.
This will get 512KB of storage for the trace buffers (the minimum allowed) and reduce memory requirements.
To do this, look for the following lines in the trace.dat file pointed to by the JVM properties file:
com.ibm.ejs.*=all=disable com.ibm.ws390.orb=all=disableEnsure that both lines are set to =disable or delete the two lines altogether.
Note: If ras_trace_outputLocation is set, you may be tracing and not know it.