This SupportPac provides instructions for changing the queue limits.
WebSphere MQ has many limits built into the system. These are designed to prevent out-of-control applications obtaining important system resources that prevent a balanced workload from operating properly. Customers have stated that two of these limits in particular (maximum amount of bytes in a queue and maximum amount of memory (RAM) reserved for non-persistent messages) are hampering normal operations. Therefore, a mechanism for changing these two limits has been introduced.
This SupportPac provides instructions for changing the limits associated with the maximum amount of bytes in a queue and the maximum amount of memory reserved for non-persistent messages. However, these limits should be altered only after careful consideration of the potential benefits; change only those queue definitions that require the additional function.
Skill Level Required
Users of this SupportPac need to have expert knowledge of WebSphere MQ on the platform they are tuning.
New in this Release
The following changes have been made in this release:
» Updated for WebSphere MQ v7.0 onwards.
Owner: Paul Harris, WebSphere MQ Performance, Hursley
First Release: 17Dec97
Last release: 17Jul12
Current Version: 1.2
»Please note that the version number shown in the right-hand pane is the version of the WebSphere MQ or WebSphere MB product that this SupportPac applies to. The date is the last webpage refresh.
To view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage.
The SupportPac requires:
» WebSphere MQ v7.0 or later on distributed platforms.
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options|
|mp01.pdf||17 Jul 2012||US English||33357||FTP|
Category 2 SupportPacs are provided in good faith and AS-IS. There is no warranty or further service implied or committed and any supplied sample code is not supported via IBM product service channels.
You may submit a question or offer feedback on the SupportPac but please be aware that a response is NOT guaranteed.