Different message buffer size for different DBs in the same

The -Mm parameter is a startup option and not a DB connection option. So one client can only talk to databases with the same -Mm setting.

I believe that chaning -Mm to a connection parameter (or inheriting it from the DB) has been discussed but not implemented.

For the pf issue... Progress is most likely using the last -Mm option in the pf.

that’s coming in 11.6

To add a little more detail to what has already been stated:

Unfortunately no, in release 11.5 and prior the last specification of the –Mm value in the .pf file is the one used for each database connection listed in the .pf file or on future “connect” statements.

Progress has planned to enhance the –Mm behavior in OE 11.6 where the server will dictate the –Mm setting and the –Mm specified on the client connection is ignored unless optionally enforced.

With that, a user can connect to multiple database servers of differing –Mm settings and DBAs can change the -Mm for a server without the need to rollout new connection parameters to clients.

Thanks everyone. Really helpful.

You can connect to a database with different -Mm if you use a shared memory connection for that database. The -Mm is not relevant for that connection.

Start another login broker with the -Mm that matches the parameter's value at client's startup.