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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
MQ submits SQL requests up to every 5 seconds. DB2 DBRMs CSQ5L221 and
CSQ5S221 are referenced.
There is no data for them to retrieve, resulting in the SQLCODE 100
being returned. Because it receives no data MQ issues a rollback
resulting in thread aborts. There is the overhead of DB2
abort/rollbacks being issued every 5 seconds.
.
The suggestion was for MQ to check for return code 0 or 100 to
commit.
Please refer to IBM PMR case TS016662082
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
From an MQ perspective this is working as designed. We haven't been able to identify any noticeable performance impact from this behaviour which has been part of the MQ design since queue sharing group support was added many years ago.