This topic applies only on the z/OS operating system.

Trace controls for IBM service

Use these settings to view or modify your trace settings.

To view or set your trace settings, use the WebSphere administrative console:
Note:
  • If you use any level of tracing, including ras_trace_defaultTracingLevel=1, ensure that you set ras_trace_outputLocation to BUFFER.

    ras_trace_defaultTracingLevel=1 will write exceptions to the trace log as well as to the ERROR log.

  • Set the ras_trace_BufferCount=4 and ras_trace_BufferSize=128.

    This will get 512KB of storage for the trace buffers (the minimum allowed) and reduce memory requirements.

  • It is best to trace to CTRACE.

    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.

  • Make sure you disable JRAS tracing.
    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=disable
    
    
    
    Ensure 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.
ras_trace_defaultTracingLevel= n
Specifies the default tracing level for WebSphere Application Server for z/OS.
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
Use this variable together with the ras_trace_basic and ras_trace_detail variables 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
ras_trace_basic=n | (n,...)
Specifies tracing overrides for particular WebSphere Application Server for z/OS subcomponents.

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_defaultTracingLevel variable.
Note: Valid values for ras_trace_basic are:
  • 0: RAS
  • 1: Common Utilities
  • 2: COS/Naming
  • 3: COMM
  • 4: ORB
  • 5: IM
  • 6: OTS
  • 7: Shasta
  • 8: Systems Management
  • 9: OS/390 Wrappers
  • A: Daemon
  • B: IR
  • C: Test
  • D: COS/Query
  • E: Security
  • F: Externalization
  • G: Adapter
  • H: Lifecycle
  • I: Identity
  • J: JRAS (internal tracing--via direction from IBM support)
  • K: Reference collections
  • L: J2EE

Default: (no default value)

Example:
 ras_trace_basic=3
ras_trace_detail=n | (n,...)
Specifies tracing overrides for particular WebSphere Application Server for z/OS subcomponents.

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_defaultTracingLevel variable.
Note: Valid values for ras_trace_detail are:
  • 0: RAS
  • 1: Common Utilities
  • 2: COS/Naming
  • 3: COMM
  • 4: ORB
  • 5: IM
  • 6: OTS
  • 7: Shasta
  • 8: Systems Management
  • 9: OS/390 Wrappers
  • A: Daemon
  • B: IR
  • C: Test
  • D: COS/Query
  • E: Security
  • F: Externalization
  • G: Adapter
  • H: Lifecycle
  • I: Identity
  • J: JRAS (internal tracing--via direction from IBM support)
  • K: Reference collections
  • L: J2EE

Default: (no default value)

Examples:
 ras_trace_detail=3
 ras_trace_detail=(3,4)
ras_trace_specific=n | (n,...)
Specifies tracing overrides for specific WebSphere Application Server for z/OS trace points.

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]
ras_trace_exclude_specific=n | (n,...)
Specifies WebSphere Application Server for z/OS trace points to exclude from tracing activity.

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]



Related tasks
Diagnosing problems (using diagnosis tools)
Related reference
IBM service call preparation
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 9:31:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=rtrbibmonlytracecontrols
File name: rtrb_ibmonlytracecontrols.html