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.


Add a new idea Subscribe
Status Under review
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Jul 31, 2026

RELATED IDEAS

Enable message segmentation beyond negotiated MAXMSGL for MQ client connections

Environment: MQ LTS 9.4.0.20 on CP4I 16.1.0, OpenShift 4.20 (Azure). IBM ACE v13 on the same cluster connects via SVRCONN over the cluster-internal network. MAXMSGL is set to 100 MB on queue manager, queue, and channel.


Summary: For MQ segmentation in server applications, MQPUT segments messages up to nearly 2 GiB, but client applications are limited to 100 MiB by the MAXMSGL negotiated between the CLNTCONN and SVRCONN channels. Messages larger than precisely 104857600 bytes fail with MQRC_DATA_LENGTH_ERROR (reason code 2010).

Please read the blog: https://community.ibm.com/community/user/blogs/morag-hughson/2026/06/07/morags-quirks-18-segmentation


Use case/ACE Integration: An ACE flow reads database rows, maps them via DFDL, Base64-encodes the payload into JSON (>105 MB), and sends it to another ACE integration via MQ with "Segmentation allowed" set on the MQOutput node. This works in bindings mode (ACE and MQ on one host) but fails on CP4I over SVRCONN: [An error occurred in 'demand.GetDemandFromPDA.KIP000.AZUREBLOB.BLOBDATA' when writing message to queue 'KIP000.AZUREBLOB.BLOBDATA' on queue manager 'QMGR1'. State = '-1' 'MQW102' '2010' '' 0x000007da MQRC_DATA_LENGTH_ERROR]


The request: Enable client applications to put/get segmented messages exceeding the channel-negotiated MAXMSGL, as server applications can. In containerized platforms (CP4I), client connections are the only option, so this is a functional parity gap, not an enhancement of convenience.

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.