(ZOS) Trace controls for IBM Support

Use these settings to view or modify the trace settings.

To view or set your trace settings, in the administrative console:

• Click Environment > WebSphere variables.

• On the Configuration Tab check for any of these properties in the name field and observe the property settings in the value field.

• To change or set a property, specify the property name in the name field and specify the setting in the value field. We can also describe the setting in the description field on this tab.

• If we use any level of tracing, including setting the ras_trace_defaultTracingLevel property to 1, verify that we set the ras_trace_outputLocation property to BUFFER.

  When the ras_trace_defaultTracingLevel property is set to 1, exceptions are written to the trace log, as well as to the ERROR log.

• Set the ras_trace_BufferCount property to 4, and the ras_trace_BufferSize property to 128.

  These settings reserve 512KB of storage for the trace buffers, which is the minimum amount of storage that can be used, and reduces memory requirements.

• It is best to trace to CTRACE.

  If we are tracing to SYSPRINT with the ras_trace_defaultTracingLevel property set to 3, we might experience an almost 100% throughput degradation. If we are tracing to CTRACE, however, we might only experience a 15% degradation in throughput.

• Make sure you disable JRAS tracing.

  To disable JRAS tracing, find the following lines in the trace.dat file that is 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. If the ras_trace_outputLocation property is set, we might be tracing and not know it.

bprac

ras_trace_defaultTracingLevel= n

Default tracing level for the product.

Value	Description
0	No tracing
1	Exception tracing
2	Basic and exception tracing
3	Detailed tracing, including basic and exception tracing

Use this property, together with the ras_trace_basic and ras_trace_detail properties, to set tracing levels for the product subcomponents. Default tracing level for the product.

Default: 1

Example:

 ras_trace_defaultTracingLevel=2

ras_trace_basic=n | (n,...)

Tracing overrides for particular subcomponents.

Subcomponents, specified by numbers, receive basic and exception traces. If IBM Support directs you to specify more than one subcomponent, use parentheses and separate the numbers with commas. IBM Support provides the subcomponent numbers and their meanings.

Other parts of the product receive tracing as specified on the ras_trace_defaultTracingLevel variable.

Valid values for this property 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
• M: Logging
• N: GlueCode

Default: (no default value)

Example:

ras_trace_basic=3

ras_trace_detail=n | (n,...)

Tracing overrides for particular subcomponents.

Subcomponents, specified by numbers, receive detailed traces. If IBM Support directs you to specify more than one subcomponent, use parentheses and separate the numbers with commas. IBM Support provides the subcomponent numbers and their meanings.

Other parts of the product receive tracing as specified on the ras_trace_defaultTracingLevel variable.

Valid values for this property 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
• M: Logging
• N: GlueCode

Default: (no default value)

Examples:

 ras_trace_detail=3

 ras_trace_detail=(3,4)

ras_trace_specific=n | (n,...)

Tracing overrides for specific product trace points.

Trace points are specified by 8-digit, hexadecimal numbers. If IBM Support directs you to specify more than one trace point, use parentheses and separate the numbers with commas. We also can specify a property name by enclosing the name in single quotes. The value of the is handled as if you had specified that value on the ras_trace_specific property.

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 product trace points to exclude from tracing activity.

Trace points are specified by 8-digit, hexadecimal numbers. If IBM Support directs you to specify more than one trace point, use parentheses and separate the numbers with commas. We also can specify a property name by enclosing the name in single quotes. The value of the property is handled as if you had specified that value on the ras_trace_exclude_specific property.

Default: (no default value)

Examples:

 ras_trace_exclude_specific=03004020

 ras_trace_exclude_specific=(03004020,04005010)

 ras_trace_exclude_specific='xyz'

where xyz is a property name]

 ras_trace_exclude_specific=('xyz','abc',03004021)

where xyz and abc are property names

Diagnose problems (using diagnosis tools)

IBM service call preparation