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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM MQ
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM MQ
The RESET QSTATS command is inherently unreliable. There is no way to ensure integrity since the only way to get the stats is to globally set them back to zero. Even the strictest controls cannot ensure that only one entity ever issues RESET QSTATS and there's no indication to any entity using these that another has interfered with their numbers.
That's OK for the most casual use cases but absolutely useless as source for data to support user stories with even a moderate need for accountability, let alone a formal audit. So when we say "existing facilities can be used to meet this requirement" we are clear that "this requirement" is the one where QSTATS are used for toy use cases only, right?
MQ does already provide SMF 116 statistics that give detailed information about queue usage. These stats could be used to determine which queues are being used. There is also the RESET QSTATS command which gives some information about traffic through queues - many monitoring products use this to provide summaries.
We are considering adding further statistics and status information in future versions of MQ, but existing facilities can be used to meet this requirement.