Kbase P13785: 4GL Tracing Feature - How to enable enhanced logging feature ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/13/2005 |
|
Status: Verified
GOAL:
What can be used help troubleshooting issues related to WebSpeed
GOAL:
What can be used help troubleshooting issues related to AppServer
GOAL:
4GL Tracing Feature
GOAL:
How to trace the 4GL
GOAL:
How to enable enhanced logging feature ?
GOAL:
How to use the ?clientlog, ?logginglevel and ?logentrytypes startup parameters
FACT(s) (Environment):
Progress 9.1D
FIX:
The 4GL Tracing Feature is a diagnostic feature that was added in Progress Version 9.1D01. Note that in OpenEdge 10.x, the client logging uses a different syntax. See the Debugging and Troubleshooting guide for more information.
This feature records the execution of the following 4GL statements in a log file:
- RUN
- User-defined FUNCTIONS
- PUBLISH
- SUBSCRIBE
The destination of the messages depends on what the client type is:
-For GUI/TTY clients, the log file is the file name specified by the ?clientlog startup parameter.
-For AppServer and WebSpeed, the messages go to the existing server log file.
4GL Tracing is enabled when the logginglevel parameter is set to 4, and the logentrytypes parameter is set to 2. To set these parameters:
- For GUI/TTY clients, specify the startup parameters ?logginglevel 4 ?logentrytypes 2.
For example:
prowin32.exe ?clientlog mylog.lg ?logginglevel 4 ?logentrytypes 2
-For AppServer/WebSpeed, set srvrLoggingLevel to 4 and srvrLogEntries to 2 in the ubroker.properties file.
For example:
srvrLoggingLevel=4
srvrLogEntries=2