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 Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Jul 17, 2019

DataPower Support for MQMD version 2 headers and MQMD Extended Data Segments

We had a production issue wherein an MQ message from IIB to DataPower can take one of two paths. If it goes over MQ 7.1, it gets into DataPower just fine. If it goes over MQ9.1, it fails. The problems is that the message has an MQMD version 2 header with a group ID.... when that message flows over MQ 9.1, a recent change in that version of MQ causes the conversion of the header to MQMD v1 to create an MQMDE extension data segment which DataPower does not know how to read/process. As such, DataPower tries to decode the inbound XML starting with the extended data rather than the actual (xml) data, and fails due to that not being valid XML data. Request to IBM: To ensure that DataPower is upgraded quickly to provide complete support for MQ version 9.1, including the ability to handle MQMD version 2 headers as well as MQMD extended data segments across all MQ-related functions including (but not limited to) MQ front side handlers, MQ-based url-open extension function, MQFTE front side handlers, etc.

Idea priority High
RFE ID 134685
RFE Product IBM DataPower Gateways