Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Delivered
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
RFE ID 150569
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |
    Dec 15, 2023
    The EnvironmentScope=Connection option enables this
  • Admin
    Mark Taylor
    Reply
    |
    Dec 8, 2021

    We hope to deliver a solution to this in a future version of MQ