rdisp/TRACE* Parameters

You can use the rdisp/TRACE* profile parameters to set the level of detail and the components that write traces.

You can change the parameters dynamically with the exception of rdisp/TRACE_COMPS, thus changing the trace behavior in productive operation.

Integration

You need these parameters for trace logging.

Features

The following table lists the parameters and their meanings.

Trace Parameters
Parameter	Meaning	Value Range, Example
`rdisp/TRACE`	You use this parameter to set the trace level for the `dev_*` developer trace. The following values are permitted: Caution Trace level `2` or higher affects the performance of the system and should only be set for an error analysis. The 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 located. You can use the `rdisp/TRACE_LOGGING` parameter to prevent the trace files from getting too big. End of the caution.	Whole number between `0` and `3`: `0`: No trace. `1`: Error messages are 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.
`rdisp/TRACE_COMPS`	Each SAP component has an abbreviation (see Trace Components). This parameter controls the status of the components as follows. Component X Is inactive if 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 as a lowercase letter Writes the trace with a higher level if the component is contained in the string as an uppercase letter (and `rdisp/TRACE` is set accordingly)	Character string consisting of letters for the trace components and the strings `All` or `all`. Example You want all components to write the trace up to level `1`. Thereafter, you only want the task handler components to write the trace. Set the string to `Mdyabcirplesxn`. To avoid long strings, you can start the string with `ALL` (all letters uppercase) or `all` (all letters lowercase) and then list possible exceptions. `rdisp/TRACE_COMPS =all, M` Meaning: All components to level `1`, thereafter only task handler components. This is also the default setting. `rdisp/TRACE_COMPS =All, ads` Meaning: All components up to the highest level, but not diag, ABAP, or spool. End of the example. Caution If the parameter does not work as intended, formulate the string so that it begins with `all` or `All`. End of the caution.
`rdisp/TRACE_LOGGING`	This parameter activates trace logging.	The parameter values must have the following syntax: Syntax rdisp/TRACE_LOGGING = on, <n> [k m] [global=on off] off End of the code. 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_0` `rdisp/TRACE_PATTERN_1` `rdisp/TRACE_PATTERN_2`	`rdisp/TRACE_PATTERN_<xx>` (`<xx>=0,1,2`) defines a search pattern to automatically switch off the SAP trace. This parameter only has an effect if trace logging is activated using `rdisp/TRACE_LOGGING`rdisp/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 dev_w* work process trace files `dev_disp` dispatcher trace files `dev_rd` gateway trace files `dev_icm` ICM trace file (if available) `dev_ms` message server trace file (if available) 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 that can contain the special characters `` or `?`. Caution 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. End of the caution. Example Pattern `"word1 word?"` is found in line `"one example with word1 and word2"` but not in line `"one example with word1 and word"` Pattern `"10 \* 10 ="` is found in line `"Multiplication: 10 * 10 = 100"` but not in line `"Addition: 10 + 10 = 20"` End of the example.
`rdisp/TRACE_SEARCH_LIST`	You can use this parameter to specify a list of trace file types to be included in the automatic trace search. More information: Trace Logging	Special character string. As a value for this parameter, you can enter a list with the following elements (use a comma or a semicolon to separate elements): `ALL`, `DISP`, `WP`, `GWRD`, `MS`, `ICMAN` Example `rdisp/TRACE_SEARCH_LIST = WP, ICMAN` Meaning: All work process trace files and the ICM trace file are included in the search. End of the example.
`rdisp/TRACE_RESOLUTION`	You can use this parameter to control the frequency of the timestamp in the trace files. It specifies how often per second a timestamp is to be written. The default value for this parameter is `1`, which means that (at least) one second must separate the timestamps. `0` deactivates the writing of timestamps. With a parameter value `> 0`, the milliseconds of the timestamp are displayed in the following format: `"Fri Sep 3 14:47:54:433 2004"`	Whole number (between 0 and 10) Example `0`: No timestamp is written `1`: A maximum of one timestamp is written per second (old behavior) `5`: A maximum of five timestamps are written per second (at least 200ms separate the timestamps) `10`: A maximum of ten timestamps are written per second (at least 100ms separate the timestamps) End of the example.