Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Changing the size is not practical as has already been said. The usual recommendation is simply to give the log file the maximum size (which is not really that large anyway with current storage systems), and do tuning by changing the number of active/secondary logs.
Most other items in the queue manager are now available to update such as the log type, number of logs etc. Would the https://www.ibm.com/docs/en/ibm-mq/9.3?topic=reference-migmqlog-migrate-mq-logs not be able to support the Log File Pages updates?
I have a number of retail customers who would like to implement this feature and it would tie in nicely with a containerised deployment approach in that if traffic loads change on the queue manager over time we can dynamically align the queue manager to changing business needs.
This is not something we plan to implement. The cost would be very high, as it would have to cover a number of scenarios including recovery from older log files with a different size from the current setting. It would also be very difficult to manage with capabilities such as NativeHA where log sizes would need to be changed simultaneously across all replicated instances.
Looking at a dev/ops environment wouldn't you be recreating the full environment anyway??
Sure in a non production environment, and it would probably not be "live" until the next bounce of the queue manager.
The only advantage for a production maintenance window would be that there may me messages on the queues...