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 2, 2022


Good Day,


I would like to suggest the following feature improvement to IBM Queues GET request, the ability to Get with a message ID or MESSAGE_UNDER_CURSOR,

Where there no messages body is sent back, saving on bandwidth and overhead of reading the messages on the server side only.
All we would like to do with this is just pop the messages off the queue and for the server to do is housekeeping no need to transmit the message.

The reason is because of MQMO.SYNC_POINT is slow, the other methods are 10-100X faster to Browse and then read the message off the queue, however,

for the second read off the queue, we don’t need the message response, we would just like to remove it from the queue, if we were to have very large payloads, this method could be slower.

We just run our transaction manager for when things were to crash to reconcile things, even if we were to use a sync point,

We can get duplicate messages, so might as well go for the faster methods as we have to have our transaction manager reconcile things.



Only respond with an aka, of found success or failure, matched or not matched and for the server to do is normal housekeeping.


Kind Regards,

Wesley Oliver.

Idea priority Low
  • Admin
    Mark Taylor
    Jan 31, 2023

    MQGMO_ACCEPT_TRUNCATED_MSG already exists for applications using the MQI. There is not likely to be any further extension to other APIs.