Did this article resolve your question/issue?



What is the -l (local buffer size) parameter?

« Go Back


TitleWhat is the -l (local buffer size) parameter?
URL NameP21349
Article Number000140209
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
What is the -l (local buffer size) parameter?
What is the local buffer used for?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
The -l parameter, is a Client parameter used to set the Local Buffer Size. This is the size of the local record buffer in which Progress stores all variables, work files and records that are in use at one time for a user.
  • The single- and multi-user default is 200, the minimum is 1, and the maximum value is 4000000 (4GB).
  • The size of the local record buffer is in 1 KB units.
The local buffer size is a soft limit; when an application needs to exceed the local buffer size, OpenEdge automatically increases it and issues a WARNING message. The WARNING is written to the current output (if there is current output) and to the log file (connected database log file (.lg), AppServer server log, client log, etc.)
WARNING: -l exceeded. Automatically increasing from <old value> to <new value>. (5408)

The -noincrwarn parameter can be used to suppresses this and related soft-limit Warning messages: (5407),(5408),(5409),(5410). Refer to Article  How to suppress warning messages (5407),(5408),(5409),(5410) from displaying on client screens.   

It is possible to force Progress to adhere to the specified -l record buffer limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When using the -hardlimit startup parameter that restricts all soft-limits (-l, -D, -nb, -mmax). For further information, refer to Article:
References to Other Documentation:

OpenEdge Deployment: Startup Command and Parameter Reference, Startup Parameter Usage Categories, Client Session parameters

Progress Article(s):
 Receiving many 5408 Warnings  
 How to troubleshoot error 6028  
Last Modified Date3/26/2021 5:37 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.