Maximum Private Buffers per Connection (-Bpmax)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Maximum Private Buffers per Connection (-Bpmax) parameter to control the number of private buffers a connection can
request through the private read-only buffers (-Bp)
parameter.
| Operating system and syntax | UNIX / Windows |
-Bpmax
n
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Database Server | 25% of -B | 1 | 64 | 64 |
- n
- An integer specifying the maximum number of private buffers.
The number of blocks in the database buffers is controlled by the blocks in
database buffers (-B) parameter. Up to 25% of the blocks
created may be allocated for use as private buffers. When a client connects to an OpenEdge
database, the connection requests -Bpn private buffers. Prior to 9.1C, the maximum value of -Bp was 64. With the -Bpmax
parameter, the broker may override this limit by allowing the value of -Bp to be up to 25% of -B.
The Maximum Private Buffers per Connection (-Bpmax) parameter may be modified while your database is online using PROMON or through the _DbParams VST. This change will only take effect on new connections to the database.
You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.