Data type:
Access:
Applies to:
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.
filename.999999.extensionFor 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. For DataServer Broker instances of the Unified Broker, the LOG-THESHOLD attribute corresponds to the srvrLogThreshold attribute defined by the DataServer Broker instance in the ubroker.properties file.To specify a log file name for ABL clients, use the LOG-MANAGER system handle’s LOGFILE-NAME attribute or the Client Logging (-clientlog) startup parameter. Use the LOG-MANAGER system handle’s NUM-LOG-FILES attribute 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.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 OpenEdge Deployment: Startup Command and Parameter Reference, OpenEdge Data Management: DataServer for Microsoft SQL Server, and OpenEdge Development: Debugging and Troubleshooting.
© 2013 Progress Software Corporation and/or its subsidiaries or affiliates. |