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

Start by posting 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 a 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.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Under review
Created by Guest
Created on May 18, 2021

MQCONNX not able to use alternative SCO

As detailed in Case number: TS004710317

Trying to develop a multi-threaded highly concurrent MQ client application connecting to many hundreds of qmgrs in a short space a time, once an MQCONNX is established to 1 qmgr, using an SCO initialized with one key store, any subsequent qmgr connections established with a new MQCONNX, reuse the first SCO initalized and not any new SCO for the new connection.

This combined with having dedicated and separate client keystores for independent and unrelated qmgrs means an entirely dedicated process is required per connection, which makes highly concurrent, high throughput threaded clients in a resource limited environment - an impossibility.

Idea Priority Low
Use Case
Highly concurrent, high throughput threaded MQ clients
RFE ID 150569
RFE Product IBM MQ

Introduce Graceful restart option for REFRESH SECURITY TYPE(SSL)

When renewing a certificate, it is necessary to refresh the ssl connecitons with the REFRESH SECURITY TYPE(SSL) command withing the queue manager.This has the affect of ending any active channels using SSL/TLS and them allowing them to restart. T...
over 2 years ago in MQ, MQ Advanced & MQ Appliance 1 Under review