Message Buffer Size (-Mm)
- Last Updated: May 2, 2024
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
Message Buffer Size (-Mm)
Use Message Buffer Size (-Mm) to specify the
standard message buffer size, in bytes. This parameter is relevant only for network
client/server connections. Message Buffer Size (-Mm) can be
specified by both the client and the server, however the size of the message buffer
specified by the server takes precedence; a value specified by the client is used as a
suggestion for initial buffer allocation, but the client then adopts the server value when
the connection is initiated.
| Operating system and syntax | UNIX / Windows |
-Mm
n
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Client Connection, Database Server | 32,600 | 350 | — | 8,192 |
- n
- The message buffer size.
OpenEdge uses message buffers to move records (messages) between servers and remote
clients. Records (plus 40-byte headers) larger than the message buffer size are fragmented
into multiple messages. If your database records are large, increase this parameter to avoid
record fragmentation. However, if the network works more efficiently with small messages,
reduce -Mm and fragment larger records.
-Mm had to agree between the client and server or the connection
would be refused. Going forward, in addition to not requiring agreement between client and
server, clients can also connect to multiple databases with different -Mm
values obtained from the server. To enforce the earlier behavior, use Enforce Mm
(-enforceMm).