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 Sep 12, 2022

Provide a Queue Status Event published when a queue has activity

There can be a lot of queues in the system and the only way to get status for "active" ones is to inquire them all (INQ QSTATUS(*) ALL. If there are 1000s of queues, these all have to be requested and yet, 90%+ of them will usually be zeros. Techniques such as using a filter do not work since only 1 filter and there are many aspects of active ones. To remediate this, the concept of a Queue Status Event is introduced. This event is published when a queue has activity. Examples of this would be when a queue is - opened for input or output - message put or get - messages expired The data published would be same as currently available when inquiring status. The data would be published the first time any activity was identified and then at most based on a system defined minimum value such as every 30 seconds. To reduce the number of events, if the queue has no change in status attributes, no event is published. As value add, max and min current depth during the interval would be useful since it would allow the publish interval to be larger and still catch some understanding of the queues behavior.
Idea priority High
  • Admin
    Mark Taylor
    Sep 27, 2022

    We do not think it likely that this would ever be implmented, at least in the form described here. Therefore this idea is being declined.

    More likely would be something to make it easier to use the published resource metrics (used by tools like amqsrua), perhaps with a combination of wildcarding and non-"null" filtering.