Integration
Hide about this portal


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.


Add a new idea Subscribe
Status Not under consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on May 25, 2021

RELATED IDEAS

Backout target for subscriber objects

See this idea on ideas.ibm.com

Many of our topic/subscriber objects are defined on the queue managers instead of being dynamically created by applications. These subscriptions then point to a queue on the same queue manager.
When the destination queue has an issue (like it being full or put disabled), it causes the messages to be directly put on the dead letter queue.

Once the messages are on the DLQ it becomes difficult to send out alerting for the responsible group. For security reasons we also can't give developers access to the DLQ.
A DLQ handler solution is not ideal as we would need to create separate rules per queue object.

A possible solution would be to have an extra parameter for subscriber objects that defines a second message destination for when the first one fails. Somewhat similar to the BOQNAME parameter for local queues.

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

    This is not something we are likely to do in MQ.

    The suggested soljution would require adding new attributes on each object which would then require individual admininistration and setting. Instead we recommend making use of the DLQ handler with wildcarded rules; that can move messages to application-specific locations if necessary. And the source for the DLQ handler is available in the samples directories so you can further customise it if you want.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.