[z/OS]

Trace control settings

The following trace options allow you to capture the information needed to detect problems.

To view or set these options, use the WebSphere® Application Server administrative console:

  1. Select Environment > WebSphere variables .
  2. Specify the variable name in the name field and specify the setting in the value field. You can also describe the setting in the description field on this tab.
ras_trace_outputLocation=SYSPRINT | BUFFER | TRCFILE
Specifies where you want trace records to be sent:
  • To SYSPRINT
  • To a memory buffer (BUFFER), the contents of which are later written to a CTRACE data set
  • To a trace data set (TRCFILE) specified on the TRCFILE DD statement in the start procedure for the server.
    Avoid trouble Avoid trouble: [Updated in July 2012] Setting ras_trace_outputlocation to TRCFILE requires that you manually modify the start procedure for the new WebSphere Application Server to include a TRCFILE DD statement. This manual modification must be performed before the new WebSphere Application Server and associated daemons are started. [Updated in July 2012]
    jul2012
    gotcha
For servers, you can specify one or more values, separated by a space. For clients, you can only specify SYSPRINT.
Defaults:
  • For clients, SYSPRINT
  • For all other processes, BUFFER

Example: ras_trace_outputLocation=SYSPRINT BUFFER

ras_time_local=0 | 1
Specifies whether timestamps in trace records use Greenwich Mean Time (GMT) or local time. This variable setting controls timestamp format in the error log, and in traces sent to SYSPRINT or TRCFILE DD.

Default: 0 (GMT)

Example: ras_time_local=1 sets timestamps to local time.

Daemon_ras_trace_ctraceParms=SUFFIX | MEMBER_NAME
Identifies the CTRACE PARMLIB member. The value can be either:
  • A two-character suffix, which is added to the string CTIBBO to form the name of the PARMLIB member, or
  • The fully specified name of the PARMLIB member. A fully specified name must conform to the naming requirements for a CTRACE PARMLIB member.
If this environment variable is specified and the PARMLIB member is not found, the default PARMLIB member, CTIBBO00, is used. If neither the specified nor the default PARMLIB member is found, tracing is defined to CTRACE, but there is no connection to a CTRACE external writer.
Note: The Daemon is the only server that recognizes this environment variable.

Default: 00 (the default PARMLIB member, CTIBBO00)

Example: Daemon_ras_trace_ctraceParms=01 identifies PARMLIB member CTIBBO01

ras_trace_BufferCount= n
Specifies the number of trace buffers to allocate. Valid values are 4 through 8.

Default: 4

Example: ras_trace_BufferCount=6

ras_trace_BufferSize= n
Specifies the size of a single trace buffer in bytes. You can use the letters K (for kilobytes) or M (for megabytes). Valid values are 128K through 4M.

Default: 1M

Example: ras_trace_BufferSize=2M




Related tasks
Adding logging and tracing to your application
Related reference
Dump control settings
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=rtrb_tracecontrols
File name: rtrb_tracecontrols.html