IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Future consideration
Workspace z/TPF Product Family
Categories z/TPF
Created by Guest
Created on Jan 8, 2026

RELATED IDEAS

One of our customers is complaining about the inefficiency of IBM Business Events Unordered Dispatch Queue using a default 32,000 byte buffer for their larger Event Message Feeds which exceed the default buffer length and results in MQGET/decompressing the message twice. The customer is planning on turning on Compression for IBEV.UNORDERED.DISPATCH.QUEUE; however, they are requesting we increase BEVQ_DEFAULT_BUFFER_LENGTH in bevq.cpp:

Inefficient behavior:
BEVQ allocates a 32000 byte buffer to read the messages, if the buffer is not large enough the MQGET has decompressed the message it then returns MQRC_TRUNCATED_MSG_FAILED, and leaves the message on the queue. It then reallocates the buffer large enough for the message and then issues another MQGET in which case the message is retrieved and again decompressed.

By original design, IBEV does not use the maximum message length defined by the queue to determine its buffer length. It unconditionally sets it to 32000, as defined by the #define mentioned at the beginning of this case, BEVQ_DEFAULT_BUFFER_LENGTH.

Guaranteed Delivery for JVM for Kafka does set the buffer length to the maximum message length defined for the queue. This is done through an MQINQ with the MQIA_MAX_MSG_LENGTH qualifier specified. If the value can not be determined through MQINQ, it defaults to 500000.

Idea priority Urgent

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.