To view or set your trace settings, use the WebSphere administrative console:
Note:
ras_trace_defaultTracingLevel=1 will write exceptions to the trace log as well as to the ERROR log.
This will get 512KB of storage for the trace buffers (the minimum allowed) and reduce memory requirements.
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.
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.
Valid values and their meanings are:
0 | No tracing |
1 | Exception tracing |
2 | Basic and exception tracing |
3 | Detailed tracing, including basic and exception tracing |
ras_trace_basicand
ras_trace_detailvariables to set tracing levels for WebSphere Application Server for z/OS subcomponents.Specifies the default tracing level for WebSphere Application Server for z/OS.
Default: 1
Example:
ras_trace_defaultTracingLevel=2
Subcomponents, specified by numbers, receive basic and exception traces. If IBM service directs you to specify more than one subcomponent, use parentheses and separate the numbers with commas. IBM service provides the subcomponent numbers and their meanings.
Other parts of WebSphere Application Server for z/OS receive tracing as specified on the
ras_trace_defaultTracingLevelvariable.
Note: Valid values for ras_trace_basic are:
Default: (no default value)
Example:
ras_trace_basic=3
Subcomponents, specified by numbers, receive detailed traces. If IBM service directs you to specify more than one subcomponent, use parentheses and separate the numbers with commas. IBM service provides the subcomponent numbers and their meanings.
Other parts of WebSphere Application Server for z/OS receive tracing as specified on the
ras_trace_defaultTracingLevelvariable.
Note: Valid values for ras_trace_detail are:
Default: (no default value)
Examples:
ras_trace_detail=3
ras_trace_detail=(3,4)
Trace points are specified by 8-digit, hexadecimal numbers. If IBM service directs you to specify more than one trace point, use parentheses and separate the numbers with commas. You also can specify a WebSphere variable name by enclosing the name in single quotes. The value of the WebSphere variable will be handled as if you had specified that value on
ras_trace_specific.
Default: (no default value)
Examples:
ras_trace_specific=03004020
ras_trace_specific=(03004020,04005010)
ras_trace_specific='xyz'[where xyz is an environment variable name]
ras_trace_specific=('xyz','abc',03004021)[where xyz and abc are environment variable names]
Trace points are specified by 8-digit, hexadecimal numbers. If IBM service directs you to specify more than one trace point, use parentheses and separate the numbers with commas. You also can specify a WebSphere variable name by enclosing the name in single quotes. The value of the WebSphere variable will be handled as if you had specified that value on
ras_trace_exclude_specific.
Default: (no default value)
Examples:
ras_trace_exclude_specific=03004020
ras_trace_exclude_specific=(03004020,04005010)
ras_trace_exclude_specific='xyz'[where xyz is an environment variable name]
ras_trace_exclude_specific=('xyz','abc',03004021)[where xyz and abc are environment variable names]