Programs that issue a lot of MQPUT calls within syncpoint, without committing them, can cause performance problems. Affected queues can fill up with messages that are currently unusable, while other tasks might be waiting to get these messages. This has implications in terms of storage, and in terms of threads tied up with tasks that are attempting to get messages.
As a general rule if you have multiple applications processing a queue you usually get the best performance when you have either
for each syncpoint. If there is only one application processing the queue, you must have more messages for each unit of work.
You can limit the number of messages that a task can get or put within a single unit of recovery with the MAXUMSGS queue manager attribute. See the ALTER QMGR command in the WebSphere MQ Script (MQSC) Command Reference for information about this attribute.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsaq0357 |