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 Feb 10, 2023

MQ Channel Identification onconnectivity issues using SSL

Difficult to identify SVRCONNs that fail to connect to MQ with certain issues with Certificates for example. MQ informs of an error from Channel ???????. On large QMGRS with many different SVRCONN's it can be difficult to try to determine which is having the issue It would be useful if it could display the Channel Name. It does give From "IP Address" but if this is coming via a network device it only shows that and not actual host.

Idea priority Medium
  • Admin
    Mark Taylor
    Reply
    |
    Apr 18, 2023

    In most cases it is impossible to know at this stage of the connection which channel might have been intended as the channel name is not yet sent. We know only what is provided during the failed TLS handshake (address, certificate etc).

    While SNI information sent from the initiator MIGHT contain a channel name, this is not going to be the default or common behaviour. It would only be available in a very limited subset of cases, which would then cause inconsistency in the insrets available.


    Therefore this Idea is being declined.