You can specify the name of the log file to which OpenEdge writes all errors and warning messages by using the following:
The Client Logging (-clientlog) startup parameter
The LOGFILE-NAME attribute on the LOG-MANAGER system handle
The logFile and related properties in the ubroker.properties file with OpenEdge Management or OpenEdge Explorer
Note: Use the above to log specifications to designate log file information for DataServer clients as well. The server context of DataServers, however, starts with a default log file name of dataserver.lg and uses separate mechanisms for designating a log file name. See the DataServer Guide for MS SQL Server for more information about specifying a log filename for the server context.
The following table shows how to specify the log filename.
Table 26. Specifying the log filename
Method
General syntax
Example
Startup parameter
-clientlogfilename
-clientlog mylog.log
LOG-MANAGER system handle
LOG-MANAGER:LOGFILE-NAME
= "filename"
LOG-MANAGER:LOGFILE-NAME = "mylog.log"
OpenEdge Management or OpenEdge Explorer, or ubroker.properties files
Note: After starting an ABL session using the Client Logging (-clientlog) startup parameter, another log filename can be specified in code using the LOGFILE-NAME attribute on the LOG-MANAGER system handle. In this case, OpenEdge stops writing to the log file specified by the Client Logging (-clientlog) startup parameter and starts writing to the log file specified by the LOGFILE-NAME attribute.
For a detailed description of the Client Logging (-clientlog) startup parameter, see OpenEdge Deployment: Startup Command and Parameter Reference. For a detailed description of the LOG-MANAGER system handle, see OpenEdge Development: ABL Reference.
For more information on ubroker.properties, see the ubroker.properties.README file in $INSTALLDIR/properties/ubroker.properties.README.
To use OpenEdge Management or OpenEdge Explorer to view and set properties, see Logging settings .
The Client Logging (-clientlog) startup parameter