Progress
Startup Command and Parameter
Reference


Debug Alert (-debugalert)

Operating 
System
and
Syntax 
UNIX
Windows 
-debugalert 
Use
With 
Maximum
Value 
Minimum
Value 
Single-user
Default 
Multi-user
Default 
CS

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:

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