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 May 11, 2024


If an application forgets to set Expiry on their messages and therefore gets the default MQEI_UNLIMITED, an administrator can override that using the queue attribute CAPEXPRY. If an application didn't forget and has messages that should never be expired, they have no way to convey that their messages are different and should not have Expiry set. Request a new constant, e.g. MQEI_NEVER with value -2, that cannot be overridden by CAPEXPRY and implies Unlimited Expiry.
Idea priority Medium
  • Guest
    May 14, 2024

    I was actually imagining the situation where an MQ administrator does not realise that they shouldn't set CAPEXPRY on a queue - imagine they did it to the SYSTEM.CLUSTER.REPOSITORY.QUEUE as a thought experiment. How can an application protect itself against that situation?

  • Admin
    Mark Taylor
    May 14, 2024

    An interesting suggestion, but not something we would plan to do.

    If an application developer really wants to override the administratively-decided expiry, then they could instead ask for a different queue path without CAPEXPRY set.