rdisp/TRACE* Parameters


With the profile parameters rdisp/TRACE*you can set the level of detail and the components that write traces.

You can change the parameters dynamically with the exception of rdisp/TRACE_COMPS, and in doing so change the trace behavior in productive operation.


You need the parameters particularly for Trace Logging.


The following table lists the parameters.

Trace Parameters



Value Range, Example


With this parameter you can set the trace level for developer traces dev_*. The following values are permitted:

Trace level 2 or higher affects the performance of the system and should only be set for an error analysis. Apart from this trace files also grow very quickly when trace logging is activated. Check that there is enough space on the hard drive where the SAP directory is. With parameter rdisp/TRACE_LOGGING you can prevent that the trace files get bigger than a certain size.

Whole number (between 0 and 3)

0:  No trace

1:  Error messages written to the trace file.

2:  Full trace. The trace entries are dependent on the SAP program traced.

3: Like 2 , but data blocks are also traced.


Each SAP component has an abbreviation (see Trace Components).

This parameter controls the status of the components as follows.

Component X

·        Inactive when the code letter is not in the string (no trace at all)

·        Writes the trace only to level 1 (error), if the component is contained in the string only with a lower case letter.

·        Writes the trace also with a higher level when the upper case letter is contained (and rdisp/TRACE is set accordingly).

Character string consisting of letters for the Trace Components and the strings All or all.

You want all components up to level 1 write the trace and that higher than this only the task handler components write the trace. Then set the string to value Mdyabcirplesxn. To avoid such long strings you can start the string with "ALL" (all letters upper case) or "all" (all letters lower case) and then list possible exceptions.

rdisp/TRACE_COMPS  =all, M

means all components up to level 1, beyond this only task handler components. This is also the default setting.

rdisp/TRACE_COMPS =All, ads

means all components up to the highest level, but not diag, ABAP, or spool.

If the parameter should not take affect, formulate the string so that it begins with all or All.


This parameter activates the Trace Logging.

The parameter values must have the following syntax:

rdisp/TRACE_LOGGING = on, <n> [k   m] [global=on off]   off

The first part specifies that logging is active. The value here can be either ON or OFF. If logging is active, you can specify the file size in the second part.




rdisp/TRACE_PATTERN_<xx> (<xx>=0,1,2) defines a search pattern to switch off the SAP trace automatically. This parameter has effect only if trace logging is activated using Trace Logging In this case, the trace files are searched for the search pattern before being automatically reset. If the pattern is found, trace logging is deactivated and the trace level is reset to 1. The following trace files are included in the search:

·        All work process trace files dev_w*

·        Dispatcher trace file dev_disp

·        Gateway trace file dev_rd

·        ICM trace file (if available) dev_icm

·        Message server trace file (if available) dev_ms

 The search pattern can contain the special character * for any character string, and ? for any character. Use the backslash (\) to ensure that special characters are treated as ordinary characters.

Character string which can contain the special characters * or ?

For the sake of readability, the search patterns in the following examples are enclosed in inverted commas. When specifying your own search terms in RZ11 or in the profiles, however, enter them without inverted commas.


"word1 * word?"

is found in line

"one example with word1 and word2", but not in line "one example with word1 and word"


"10 \* 10 ="

The pattern "10 \* 10 =" is found in the line "Multiplication: 10 * 10 = 100", but not in the line "Addition: 10 + 10 = 20".


With this parameter you can specify a list of trace file types that is to be included in the automatic trace search (see Trace Logging).

Special character string.

A list with the following elements, separated by a comma or semicolon can be specified as the value: ALL, DISP, WP, GWRD, MS, ICMAN (see Trace Logging ® Specify Trace Components)


means that all work process trace files and the ICM trace file can be included in the search.


With this parameter you can control the frequency of the time stamp in the trace files. It specifies how often per second a time stamp is to be written. The default value for this parameter is 1 and means that (at least) one second must separate the time stamps. Value 0 deactivates the writing of time stamps.

With a parameter value > 0, the milliseconds of the time stamp are displayed in the following format:

"Fri Sep  3 14:47:54:433 2004"

Whole number (between 0 and 10)

0: No time stamp is written

1: Maximum one time stamp is written per second (old behavior)

5: A maximum of five time stamps are written per second (at least 200ms separate the time stamps)

10: A maximum of ten time stamps are written per second (at least 100ms separate the time stamps)