Developer Trace File Names
Component | File Name |
| Dispatcher | dev_disp |
Work Process | |
Task handler | dev_w<n> n is the range from 0 to one less the number of work processes. |
Dynp (screen processor) | dev_dy<n> |
Roll | dev_ro<n> |
Paging | dev_pg<n> |
DB interface | dev_db<n> |
ABAP processor | dev_ab<n> |
Enqueue (lock) | dev_eq<n> |
Logging | dev_lg<n> |
Spool | dev_w |
Message server | dev_ms<n> |
SAPGUI (presentation) | dev_st<logon name> |
APPC-server (CPIC gateway) | dev_appc |
RFC (Remote Function Call) facility | dev_rfc, dev_rfc<n> dev_rfc traces RFC calls to external functions (written in C or Visual Basic). dev_rfc<n> traces RFC calls that are executed in R/3 work processes. <n> is the number of the work process in the server (as shown above). A work process uses the same log file across RFC calls. |
Gateway | dev_rd |
R3trans and tp transport programs | dev_tp |
Monitoring infrastructure (test mode only) | dev_moni In normal operation, you will not see this file. It is used only by test tools of the monitoring infrastructure. It therefore appears only if the test tools must be activated during a support session. |
No comments:
Post a Comment