Parameter
rdisp/TRACE_COMPS
Short text
Enable/disable trace for components
Parameter Description
In the SAP system, there is a developer trace file for each work process. You can activate and deactivate the components individually. You can change the trace level and trace components at runtime using the program dpmon or with transaction SM50.
For performance and compatibility reasons, you can still set the global trace level ( rdisp/TRACE ). The “String with the active components” is new. Each component has a unique ID, consisting of an identifying letter. The following components exist:
• A (ABAP)
• B (Database)
• C (DBSL, Database interface)
• D (Diag)
• E (Enqueue)
• F (JSF, Java Startup Framework)
• G (NLS, I18N)
• H (ICF, Internet Communication Framework)
• I (Ipc)
• J (Java Virtual Machine Container)
• L (Background processing log)
• M (Task handler)
• N (SNC, Secure Network Communication)
• P (Paging)
• R (Roll)
• S (Spool)
• T (Debug system)
• W (SAP GUI for HTML, ITS)
• X (Memory management)
• Y (Dynp)
The status of the components is controlled using rdisp/TRACE_COMPS 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 correspondingly). If you wanted all components to write a trace to level 1, and only the task handler components to write a more detailed trace, you would need to set the string to the value “Mdyabcirplesxn”, for example. However, since this is much too cryptic, you can also start the string with “All” (all IDs set to uppercase) or “all” (all IDs set to lowercase), and then list any exceptions.
Examples
• rdisp/TRACE_COMPS =all, M
means
All components to level 1, thereafter 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.
Caution
If the parameter does not work as intended, formulate the string so that it begins with all or All.
Background
• There is an area in shared memory for each work process, in which the current trace level and trace string is stored, and another area in which any new values can be entered using ABAP or the program “dpmon”. The work process adopts these values when it starts its next job.
• If you want to force the work process to adopt the values immediately (only in exceptional cases; loops and so on are required ), you first need to change the values in shared memory (using ABAP or dpmon) and then send a signal to the work process using “kill -USR1 [pid]” (or USR2). If the signal handling does not find any values for level/string in shared memory, it reacts as previously, that is, USR1 lowers the level by 1, USR2 increases the level by 1.
• Trace logging allows you to control the trace for the selected components. The corresponding parameters are listed below.
Application Area
Dispatcher
Default Value
all, FJM
Who is permitted to make changes?
Only for problem analysis by SAP
Operating System Restrictions
None
Database System Restrictions
None
Are other parameters affected or dependent?
rdisp/TRACE
rdisp/TRACE_LOGGING
rdisp/TRACE_PATTERN_0
rdisp/TRACE_SEARCH_LIST
Values allowed
Character string (for examples, see above)
