Progress
Startup Command and Parameter
Reference
Debug Alert (-debugalert)
You can use the -debugalert startup parameter along with the
-clientlog
startup parameter to access 4GL stack trace information during a session.If
you set Debug Alert to yes, and use the
-clientlog
startup parameter to specify a log file name, the 4GL stack trace is written to the log file you specify with-clientlog
. Messages are written to the log file as they are encountered during a session. This applies to both batch and interactive sessions. For WebSpeed and AppServer applications, the output goes to their respective log files.The stack trace is included only for the error messages and 4GL Alert-box messages that are normally written to the file specified with
-clientlog.
NOTE: If you do not use the-clientlog
startup parameter to specify a log file, the messages are not written to a log file.When
-debugalert
is set to yes and an error occurs in a batch session for:
- A 4GL batch client, Progress records the 4GL stack trace information in the log file specified with
-clientlog
. In this case, Progress lists the stack trace information in reverse order. That is, the procedure that generated the error is written first, and the root procedure is written last.- An AppServer client or a WebSpeed agent, Progress records the 4GL stack trace information in their respective log files, also in reverse order. If you view one of these log files in the Progress Explorer, it appears in top-down order since Explorer displays log files in reverse order.
To retrieve or reset the value of this parameter at runtime, use the DEBUG-ALERT attribute of the SESSION system handle.
For more information on the DEBUG-ALERT attribute or the SESSION system handle, see the Progress Language Reference and the Progress Version 9 Product Update Bulletin .
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |