Skip to Main Content

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Apr 17, 2024

Add three fields to STATQ that are in published equivalent

STATMQI and STATQ contain almost equivalent data whether you collect statistics written to the SYSTEM.ADMIN.STATISTICS.QUEUE or the published system topics. This makes it seem like the intent is for them to be the same. STATMQI seemingly is identical, but for STATQ, the published data contains three fields that are not in the queued equivalent. These are:

  • lock contention X%

  • queue avoided puts X%

  • queue avoided bytes X%

Please add these to the queued STATQ records too.

Idea priority Medium
  • Admin
    Mark Taylor
    Apr 23, 2024

    It has never been the intention that both ways of accessing the data would be equivalent. Indeed, the purpose of the metadata approach with the published metrics was precisely to permit more flexible approaches. It would not be surprising if there were further divergence over time.