The errors in SAP System must be analyzed much deeply and Syslog information and the short dumping are not enough.
It is easy to depend on a profile variable "rdisp/TRACE", each trace and the error information are stored in each SAP components and process. This type of working was intended to support the developers of C and also known as Developer trace.
Depending on profile variable, trace and error information is stored for each SAP process and component. This mechanism was originally intended as support for C developers only, and is therefore called "Developer trace", in contrast to the "official" (syslog) SAP Trace.
Values used in profile variable "rdisp/TRACE":
rdisp/TRACE =0 store no information.
rdisp/TRACE =1 store only error information.
rdisp/TRACE =2 also store trace messages.
rdisp/TRACE =3 also fully trace data blocks.
For Tracing components "rdisp/TRACE_COMPS"
rdisp/TRACE_COMPS = all all components on
rdisp/TRACE_COMPS = all all components off
The Additionally and individual components may or may not be active with capital letters and deactivate with lowercase letter.
E Lock management
T Debug System
B Database (DBSL)
X Extended Memory
G Language Support
the profile variables are only read when the system is booted.
When necessary the changes of value TRACE for processing at runtime use the following commands under Unix:
Increase the TRACE value by 1. With USR2 signal, current stack trace is additionally generated.
Reduce the TRACE value by 1.
If TRACE = 0 then all opened TRACE files closes by itself.
With the release of Version 7 the combined C-/Java stack dump will be generated by VMC activated:
Trace Logging of Version 6.2
It might become necessary for some of the error analyses for increasing trace levels. To prevent this overflow in file system the particular is to reset Trace files.
This parameter is used to trace and becomes active for a long time, just to carry error analysis. For preventing trace files to increase in size, activate the automatic reset only when files reach to a certain set size. To prior reset, in this the trace files are being saved in log file. Thus the log file has a same name as trace file with an extension of ".old".
Valid input, formats, areas:
Parameters should have following syntax:
rdisp/TRACE_LOGGING = on, [k m] [global=on off] off
rdisp/TRACE_LOGGING = off
no Trace logging
rdisp/TRACE_LOGGING = on, 1000
Trace logging if trace file is containing more than 1000 bytes
rdisp/TRACE_LOGGING = on, 20 k
Trace logging if trace file is containing more than 20 kilobytes
rdisp/TRACE_LOGGING = on, 30 m
Trace logging if the trace file is containing more than 30 megabytes