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 Aug 26, 2014

Tunable timeout parameter for MQCONN/MQCONNX

In MQ 7.1, MQ client can use followed 2 timeout mechanism to keep SVRCONN channel alive
1. Connect_Timeout set in mqclient.ini to monitor tcp connection/handshaking timeout
2. After connection (from mq view), HBINT can keep monitoring

however, between 'socket connection establish' & 'mq connection establish', there's a gap mq client waiting qmgr response via select(), from PMR, mq client is using ccxSetTimeOut and hardcoded 180 seconds

Cust ask 'tunable' parameter for this 'hardcoded' 180 seconds timeout at this moment in order to let client can get error return in control-able specified timeout period

Idea priority High
RFE ID 58437
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
    Sep 15, 2014

    We will consider this for a future release.

    However, we believe this customer has been informed incorrectly in their PMR that the timeout is hardcoded: it is not fixed at 180, but can be overridden by MQRCVBLKTO per APAR IC46074

  • Guest
    Aug 26, 2014

    Attachment (Use case): MQ client trace & tcpdump data