Progress
Startup Command and Parameter
Reference
Client Logging (-clientlog)
filename
Name of log file used for messages and 4GL stack trace information.
If the filename you supply is a relative pathname, then a file is accessed relative to the current working directory. If the filename is an absolute pathname, then the specified file is accessed.
Client logging allows an application to automatically write all error and warning messages to the specified log file. If you use the
-clientlog
parameter at startup, all messages displayed on the screen in an alert box are also written to the log file you specified with-clientlog.
When you use the
-clientlog
startup parameter, and you also specify the-debugalert
startup parameter or set SESSION:DEBUG-ALERT to yes, the log includes a 4GL stack trace for each log entry.On connect and disconnect from a database, an entry appears in the client log file identifying the database and userid (for multi-user connections). This information can be used to relate client log messages with database log messages.
If an error message is diverted to the ERROR-STATUS system handle, and client logging is enabled, then no information is written to the log file.
In a non-interactive session, the application is configured so that the output device is associated with a file (or another device). In this configuration, when a Progress statement encounters an error, it writes the error to the output device. If client logging is enabled, then this message is also be written to the specified log file.
You can use the MESSAGE statement with the VIEW-AS ALERT-BOX to write application specific information to the screen. All information written to the screen using the MESSAGE VIEW-AS ALERT-BOX is also written to the log file.
When
-debug-alert
is on 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.
The code page used for the log file is
cpinternal
and no conversions are performed for these log files.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |