Kbase P106310: Is it possible to find out which procedure (*.p file) generated an error message?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/25/2008 |
|
Status: Verified
GOAL:
Is it possible to find out which procedure (*.p file) generated an error message?
GOAL:
How to find out the name of the 4GL procedure that generated an error message?
GOAL:
How to identify the procedure name and line number of the code that generated an error message.
GOAL:
How to debug ambiguous errors like error 78?
GOAL:
When was the Client Logging startup parameter -clientlog introduced?
GOAL:
How to use the -debugalert and the -clientlog Client Session Logging startup parameters?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.1D
OpenEdge 10.x
FIX:
Use the SESSION system handle DEBUG-ALERT attribute or the SESSION's -debugalert startup parameter. For example, executing the statement:
SESSION:DEBUG-ALERT = TRUE.
in an interactive session, generates an alert box with an OK and a HELP button if an error occurs. Choosing the HELP button lists the DEBUG ALERT stack trace that identifies the procedure and the line number where the error was generated.
When an error occurs in a batch session for a 4GL batch client, Progress records the 4GL stack trace information in the procore file. When an error occurs in a batch session for an AppServer client or a WebSpeed agent, Progress records the 4GL stack trace information in their respective log files.
Starting in 9.1D01, the Client Logging startup parameters -debugalert -clientlog were introduced. Using the client session's -debugalert -clientlog startup parameters output the same DEBUG ALERT 4GL stack trace information; including procedure name and line number; to the specified file. For example:
Interactive client session startup command line:
C:\DLC\bin\_progres.exe -debugalert -clientlog mylog.lg -p myprocedure.p
Batch client session startup command line:
C:\DLC\bin\_progres.exe -b -debugalert -clientlog mylog.lg -p myprocedure.p