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.
I'm going to decline this. The approach we have today is the right one, and if just chinit accounting records are on should be low cost.
The new QQST statistics record isn't just a copy of the accounting data that we generate for queues. It shows a summary of all the interactions with the relevant queue during the time interval. This is much more succinct and easy to work with than the existing 116 format.
The existing chinit accounting records aren't a perfect match for MQ's statistic records because there isn't necessarily going to be a single record per channel per interval. For example, server connection channels might have many different applications using them at the same time, and each application gets its own QCST record summarising the behaviour of that channel.
We could consider summarising all the channel data together, but I think you would loose much of the value you get from looking at what individual application instances are doing.
Chinit accounting records can be switched on independently of MQ's other accounting records, and targeted so that they are only collected for certain channels. This would remove any impact of collecting 116 task/queue records. If you were to do that, and the data was collected by zLDA, would that give you what you need?
Hi Jack. We have discussed this internally, and while we agree this will be beneficial for our users to leverage MQ Channel Statistics, our team doesn’t own the decision to what record this data will belong to. With that being said - I have reached out to the MQ team and we are discussing if it is possible to move the Channel Statistics from SMF_116 to SMF_115.
While we will support this general Idea, at the end of the day, the MQ team has to own this, not ZLDA. I will transfer it to them and work with those folks to see what we can do.