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.
Delivered in 9.3.3.
I strongly agree to the need which will enhance our capability to be well administrating MQ in z/OS. Please make it happen to benefit all z/OS MQ customers. Thanks.
Greetings,
Over the years and from many customers I have often heard similar requests but this time someone took to time to make the formal requests. What I have heard asked for includes:
1) A new SMF 115 subtype for queue levels statistics that are independent of the task level queue accounting.
2) Controlled at the queue level.
3) The records would include, but not limited to:
a) Base queue name
b) Counts of all MQ API requests for the interval (5 MQOPENs, 4 MQCLOSEs, etc.)
c) Counts of the successful requests
d) Total bytes processed by the gets and puts
e) Counts of persistent requests
f) Counts of persistent and non persistent bytes processed for gets and puts
As we have often seen customers struggle with the issues around RESET QSTATS and who need this type of information over a longer duration than they can capture the task accounting records for, this would be a real benefit to many for trend analysis and initial problem determination.