Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB2 (Application Component) DB2 for z/OS⤷
STU3 (Package) Development Class for Database Monitor
Basic Data
| Data Element | DB2RFCTRON |
| Short Description | Switch RFC trace on |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 20 | RFC Trace On |
| Long | 20 | RFC Trace On |
| Heading | 20 | RFC Trace On |
Documentation
Definition
The RFC library itself supports a trace capability. The default value is OFF, which means that no tracing is in effect. But due to communication or transfer problems, the trace can be changed using the R/3 transaction code ST04: Alert Router settings in SAP R/3.
Switching the trace on or off results in an update of a specific database table which is read by the ICLI Alert Router whenever an exception event will be transferred to the destination. This information is passed to the RFC library, which will write a rfc<PID>_<TID>.trc file in the directory in which the ICLI Alert Router is started when a trace is requested. PID is the ICLI Alert Router�s process ID in decimal presentation, and TID is the ICLI Alert Router�s DB2 connection thread in decimal presentation.
This trace feature should be used for diagnostic purposes, only, and when your are instructed to do so by your IBM/SAP service personnel.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 710 |
