LOGFILE-NAME attribute

The name of log file OpenEdge uses to log messages and ABL stack trace information.

Data type:

CHARACTER

Access:

Readable/Writeable for LOG-MANAGER Read-only for DSLOG-MANAGER

Applies to:

DSLOG-MANAGER system handle, LOG-MANAGER system handle

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. In Windows, the pathname cannot contain characters outside of the non-Unicode code page. See OpenEdge Development: Internationalizing Applications for more information about Unicode and code pages.

Note:

Do not include a numbered sequence in the filename. This might conflict with the rolled over log files OpenEdge creates based on your NUM-LOG-FILES attribute and LOG-THRESHOLD attribute settings.

When the specified log file is open, this LOG-MANAGER attribute is read-only. This attribute is always read-only for the DSLOG-MANAGER system handle.

For the LOG-MANAGER system handle, the LOGFILE-NAME attribute corresponds to the Client Logging (-clientlog) startup parameter. For the DSLOG-MANAGER system handle, this attribute corresponds to the DataServer Logging (-dslog) startup parameter when the client is self-service or client/server using ProBroker. For DataServer Broker instances of the Unified Broker, the read-only LOGFILE-NAME attribute corresponds to the srvrDSLogFile attribute in the ubroker.properties file.

Use the LOG-ENTRY-TYPES attribute or the Log Entry Types (-logentrytypes) startup parameter to specify one or more types of log entries you want to write to the log file. Use the LOGGING-LEVEL attribute or the Logging Level (-logginglevel) startup parameter to specify a general level at which log entries are written to the log file.

For more information about the Client Logging (-clientlog), DataServer Logging (-dslog), Log Entry Types (-logentrytypes), and Logging Level (-logginglevel) startup parameters, see OpenEdge Deployment: Startup Command and Parameter Reference, OpenEdge Data Management: DataServer for Microsoft SQL Server, and OpenEdge Development: Debugging and Troubleshooting.