Kbase P28254: What is a procore file?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/05/2009 |
|
Status: Verified
GOAL:
What is a procore file?
GOAL:
Can error messages from a procedure be written to file?
GOAL:
Can I specify a file to record error messages from a procedure?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
If an error is detected in a 4GL session, Progress records the 4GL stack trace information in the procore file.
This is sometimes useful in determining what a client was doing when it abnormally terminates.
Prior to Progress Version 9.1C, the Debug Alert (-debugalert) startup parameter provided access to 4GL stack trace information
when an error occurred during an interactive session.
If -debugalert was used when an error occurred Progress would display an alert box with a help button that displayed a dialog box containing a scrollable, read-only 4GL stack trace for the current Progress session.
In Progress Version 9.1C, the Debug Alert (-debugalert) startup parameter also provides access to 4GL stack trace information when an error occurs during a batch session.
In Progress Version 9.1D and later, the Debug Alert (-debugalert) startup parameter, when used with the new -clientlog startup parameter, provides
access to 4GL stack trace information during a session and writes this information to a log file referenced with the -clientlog parameter.
In version 9.1C, the information was written to the procore file upon abnormal termination of the session.
In Version 9.1D and later, information is written to the log file you specify with the -clientlog startup parameter.
If -clientlog is not used to specify a log file name, messages will not written to a log file and will only be visible through the error dialog within the program.