Kbase P15015: Other Server Arguments in the Progress Explorer Tool fails to set -l parameter.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/5/2008 |
|
Status: Verified
SYMPTOM(s):
Other Server Arguments in the Progress Explorer Tool fails to set -l parameter.
Add -l n using the Other Server Arguments in Progress Explorer Tools.
WARNING: -l exceeded. Automatically increasing from <old value> to <new value>. (5408)
FACT(s) (Environment):
Windows
Progress 9.x
OpenEdge 10.x
CAUSE:
The -l is a client-side, session parameter. It cannot be set on the server side (though the -L can).
FIX:
Use the -l for the client startup parameters only.
On UNIX, you would set this parameter on the client startup lines for mpro, mbpro, pro, bpro, or _progres.
On Windows, you would set this parameter on the client startup lines for mpro, mbpro, pro, bpro, or prowin32.
The -l parameter can also be set on the startup lines of AppServer and WebSpeed agents.
You can also set the -l parameter within a client parameter (pf) file for any of the above.
Progress documentation states the following about the -l:
The size of the local record buffer in 1KB units.
Use Local Buffer Size (-l) to change 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 maximum size of the local record buffer is 4GB for most
systems.
The Local Buffer Size (-l) limit is a soft limit; so if your application needs to exceed the limit, Progress 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 (LG).
You can force Progress to adhere to the specified -l limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When you use the -hardlimit startup parameter, Progress issues the WARNING message when you exceed the Local Buffer Size limit. It also issues a message that a resource limit was reached and raises an untrappable STOP condition. Note that -hardlimit also enforces the limits set by the Directory Size (-D), the Maximum Memory (-mmax), and the Nested Blocks (-nb) startup parameters, so the STOP condition is raised when any of the specified limits is reached.
Please see the Progress Startup Command and Parameter Reference at www.progress.com for further details.