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 Future consideration
Created by Guest
Created on Sep 9, 2014

Relaxing the DB2 dependency for starting shared channels

Shared channels of a queue sharing group remain in a retry status because there were problems (locked pages) with the corresponding DB2 system holding the shared channel status table. The problem is described in detail in PMR 10816,035,724.

Suggested Solution:
We suggest to store the status information necessary to start a shared channel in a shared queue instead of
DB2 tables CSQ.ADMIN_B_SCST and CSQ.ADMIN_B_SSKT, similar to the sequence number which is stored in the queue SYSTEM.QSG.CHANNEL.SYNCQ.

Idea priority High
RFE ID 58889
RFE Product IBM MQ
  • Guest
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ

  • Guest
    Nov 6, 2014

    Removal of the DB2 prereq for QSGs is a long-term strategic goal, so this is something we would like to deliver in a future version of MQ as part of that process.