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 Jun 26, 2013
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit MESNS-I-475 Persist LGETDATE LGETTIME LPUTDATE LPUTTIME between queue manager reboots.

Add a queue attribute and a channel attribute for last date those objects were used. Merged

An attribute for queues that simply recorded the last time a queue was Read(GET) from and Written To(PUT) that persists a Qmgr bounce..
Also, the same thing for channels, as well. If there was a similar attribute for channels that stated last time a message traversed the channel.
Even if just the date was shown - time isn't necessary.

Idea priority Medium
RFE ID 36571
RFE Product IBM MQ
  • Guest
    Jun 14, 2017

    This would be ideal for chlauth rules as well, so that we can delete rules that are no longer used (e.g. when an application server is decommissioned but no-one tells the MQ team.).

  • Guest
    Aug 23, 2016

    Adding comments here since RFE 93226 was marked as a duplicate of this one. To me, with MQ statistics enabled, the 'last used' information for queues and channels could be determined. However, that is not the case with MQ Client channels, which was the purpose for opening 93226 - to collect statistics for Client channels. Instead of (or along with) adding new parameters to queues and channels, could we just add channel-level statistics collection for client channels?

  • Guest
    Oct 15, 2015

    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

  • Guest
    Apr 21, 2015

    We are considering this for a future release of MQ


Provide last activity time for a queue as part of queue status

Often times queues are created and abandoned. There requirement is to provide a last activity time for a queue. Much like queue creation and alter time, this would be time stamp that indicates the queue had activity. Last activity would need to be...
7 months ago in MQ, MQ Advanced & MQ Appliance 1 Not under consideration

Statistics Data for MQI Channels

On distributed platforms, MQ provides statistical information for message channels, but not for MQI channels (server conns/client conns). To find out which MQI channels are/are not being used, we'd have to turn on MQI accounting which is much more...
over 6 years ago in MQ, MQ Advanced & MQ Appliance 1 Not under consideration

Allow CHLAUTH records to have a last invoked date & time to determine redundant rules

CHLAUTH rules should have LSTINVDA and LSTINVTI attributes that get updated when a rule is matched.
over 6 years ago in MQ, MQ Advanced & MQ Appliance 1 Not under consideration