LOG-THRESHOLD attribute

The file size threshold of log files. When the current log file becomes equal to or greater than the specified size, the AVM renames and saves the log file and creates a new log file.

Data type: INTEGER

Access: Read-only

Applies to: DSLOG-MANAGER system handle, LOG-MANAGER system handle

Valid values are:

0 — This means there is no limit other than what the operating system imposes. Specify 0 to ignore the Number of Log Files to Keep (-numlogfiles) startup parameter setting. This is the default.
Between 500,000 and 2,147,483,647 — Values are in bytes (one byte typically holds one character). You can specify a file size up to 2GB, inclusive, but not lower than 500,000.

The AVM names log files controlled by either the DSLOG-MANAGER or LOG-MANAGER system handles based on a sequence number using the following format:

Syntax

filename.999999.extension

For example, if you specify a log file named my.log, the AVM renames the log file to my.000001.log before creating a new log file.

For the LOG-MANAGER system handle, the LOG-THRESHOLD attribute corresponds to the Log Threshold (-logthreshold) startup parameter. For the DSLOG-MANAGER system handle, this attribute corresponds to the Log Threshold (-logthreshold) startup parameter when the client is self-service or client/server using ProBroker.

To specify a log file name for ABL clients, use the LOGFILE-NAME attribute of the LOG-MANAGER system handle or the Client Logging (-clientlog) startup parameter. Use the NUM-LOG-FILES attribute of the LOG-MANAGER system handle or the Number of Log Files to Keep (-numlogfiles) startup parameter to specify the number of log files to keep.

For DataServers, use the DataServer Logging (-dslog) startup parameter to specify a log file name.

Note: The LOGFILE-NAME attribute of the DSLOG-MANAGER system handle is read-only.

For more information about the Client Logging (-clientlog), DataServer Logging (-dslog), Log Threshold (-logthreshold), and Number of Log Files to Keep (-numlogfiles) startup parameters, see Startup Command and Parameter Reference, Use the Microsoft SQL Data Server, and Troubleshoot ABL Applications.