Skip to Main Content
IBM Data and AI RegTech 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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

Shorter URL for this site is: or

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.