Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

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.

IBM Employees should enter Ideas at

Status Not under consideration
Created by Guest
Created on Apr 9, 2019

Set persistence and expiry of MQ messages at the application level

Actor: User needs enhanced features

In our company, we do not define queues with persistent, but expect the application has the ability to set it as persistent in the MQMD. Additionally, messages should have a set expiry (not set to infinite). Both standards are according to MQ best practices and recommendations.

CPS currently does not enforce any type of behavior on the MQ queues with regards to data persistence, but it provides queue definitions to configure persistence at the queue level (persistence property on queue level to "true").

We wish for consistency between applications, and adherence to standards. FTM Base already uses message persistence at the application level, i.e. FTM is considering all messages flowing through the Broker as business critical and makes them persistent in the MQMD.

CPS should follow suit by using message persistence at the application/message level to ensure that business critical messages are not lost. Also, both CPS and FTM should set an expiry limit on messages.
  • Admin
    Craig Rector
    Oct 8, 2020

    If there are specific messages that need to expire that is of concern, please let us know and we may consider changing those messages.

  • Admin
    Craig Rector
    Oct 8, 2020

    We do use expiry on specific sets of applicable messages, but not all so this is partially in place. But with that said, we do not plan to make changes in this area in the next two years.