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 Not under consideration
Created by Guest
Created on Jul 15, 2019

client channel provide performance info

Client channels should be extended to provide the count of requests that were delayed.
When a channel with sharecnv(>1) is used, an application can be delayed while the channels is processing a request.
The FAP should include a bit, which is set if the channel was not able to be used immediately.
When a shared connection is used, we should have another bit to say this was delayed.

The DIS CHS command and channel stats should have 3 new fields
1) Number of flows
2) Number of flows delayed because of sharecnv
3) Number of flows delayed because of shared connection

Idea priority Medium
RFE ID 134594
RFE URL
RFE Product IBM MQ
  • Admin
    Mark Taylor
    Reply
    |
    Jul 1, 2021

    The MQ documentation already states that SHARECNV(1) should be used whenever possible as it eliminates contention on the shared network resources. See https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.mon.doc/q036143_.htm The CURSHCNV and MAXSHCNV values are reported already by DISPLAY CHSTATUS to indicate the potential for contention. It is noty likely that we would add further reporting.