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 Not under consideration
Created by Guest
Created on Dec 11, 2017

New MQ Queue Manager Event - Unknown Queue Manager Name on Connect

Please create a new MQ Queue Manager Event - Unknown Queue Manager Name on Connect. The Event Message should contain details to help identify the struggling app that is using the wrong queue manager name, things like MQ Client Channel Name and remote IP address would be extremely helpful.

Idea priority Medium
RFE ID 114106
RFE Product IBM MQ
  • Guest
    Nov 26, 2021

    We recognise that this is a valid requirement. However it doesn't fit with our delivery plans for the next couple of years.

    As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.

  • Guest
    Jul 3, 2019

    For reference the email discuss detailing the trace can be found here:

    From Tim Zielke:
    08:55:46.388632 5073.1679 RSESS:00067d 0x0000: 5453484d 00000180 00000001 00000000 |TSHM............|
    08:55:46.388632 5073.1679 RSESS:00067d 0x0010: 02913000 00000000 00000000 22020000 |..0........."...|
    08:55:46.388632 5073.1679 RSESS:00067d 0x0020: b8040000 00000178 02000000 0a080000 |.......x.... ...|
    08:55:46.388632 5073.1679 RSESS:00067d 0x0030: 00000000 4d4f4e4b 45592020 20202020 |....MONKEY |

    This is data that the queue manager is sending back to the client. At offset 0x002c, there is the hex data 0a08000. That is 2058 in little endian. This trace was run on Linux x86 (little endian processor).

    I agree this would be a nice EVENT as well as a queue manager AMQERRxx.LOG type message. I have run into many problems where the client app had a typo or some such in the queue manager name, this would have helped to shorten the problem determination time.

  • Guest
    Dec 11, 2017

    This declined RFE has come up for reconsideration and I am resubmitting it. A detailed trace on the MQ Server does show the MQ Queue Manager recognizing an incorrect QM Name being provided and the 2058 MQRC being produced by the Queue Manager, at which point it would be very helpful to also have a new Event Message generated capturing the details of the MQRC 2058. The MQRC 2058 is shown in its reversed hexadecimal representation in the trace - it will not be obvious like a bad queue name on an MQOPEN call, which shows up in plain English in the trace.

    Interesting details would be the actual QM name, the QM name the application supplied but was rejected with a MQRC 2058 by the queue manager, for MQ Clients, the source IP address and MQ SVRCONN channel, etc.