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 May 14, 2024

Improve error message shown during the configuration of a new pub/subscribe scenario using MQ Explorer,

Today, MQ 9.3, if you are adding a pub/sub configuration, is not enforcing the completion of the field Base Object when you add a new alias queue. If you leave it empty, when you put the first message you will get the error message:

Message AMQ4477. The topic string supplied is invalid. When you click on details you have:
Explanation: A topic string was missing or contained invalid characters.
Response: Ensure a topic string has been defined and that there are no invalid characters in the topic string.

That message is misleading, and most likely the support team will waste time checking the topic string instead of verify the Base Object field. Maybe we don't need a specific message for this scenario and MQ might issue the error AMQ4479 instead:

Message AMQ4479. An MQOPEN or MQPUT1 call was issued, specifying an alias queue as the target, but the BaseObjectName in the alias queue attributes was not recognized as a queue or topic name. When you click on details you have:
Explanation: This error can also occur when BaseObjectName is the name of a cluster queue that cannot be resolved successfully.
Response: Correct the queue definitions.

Or perhaps, the field Base Object might be defined as mandatory and avoid the previous scenario entirely.

The steps to reproduce this using MQ Explorer are:

1- Create a new Alias Queue, giving values for Queue Name, Description, and choose Topic for Base type. Accept all defaults proposed.
1.1- In case there is no suitable local queue to be used as destination for the subscription, create a new local queue.
2- Create a new Topic, giving values for Topic Name, Topic string (a valid one, no special characters, no duplicates), Description, choose SYSTEM.DURABLE.MODEL.QUEUE and SYSTEM.NDURABLE.MODEL.QUEUE. Accept all defaults proposed.
3- Create a new subscription, giving values for Subscription Name, Topic Name, leaving Topic String empty, and filling Destination Name with the local queue mentioned in 1.1.
4- Put a message into the alias queue created in step 1. Message AMQ4477. The topic string supplied is invalid. When you click on details you have:
Explanation: A topic string was missing or contained invalid characters.
Response: Ensure a topic string has been defined and that there are no invalid characters in the topic string.

5- Edit the Alias Queue properties to enter an invalid Base Object.
6- Put a message into the alias queue modified in step 5. Message AMQ4479. An MQOPEN or MQPUT1 call was issued, specifying an alias queue as the target, but the BaseObjectName in the alias queue attributes was not recognized as a queue or topic name. When you click on details you have:
Explanation: This error can also occur when BaseObjectName is the name of a cluster queue that cannot be resolved successfully.
Response: Correct the queue definitions.

Kind regards.

Idea priority Medium
  • Admin
    Mark Taylor
    Reply
    |
    Jun 4, 2024

    Traditionally in MQ, In general, there are few checks on inter-object relationships at definition time. That's the case for tools like Explorer as well as command line MQSC.

    This is therefore not something we would plan to implement.

    1 reply