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 Jan 3, 2022

Make MQMD consistent across platforms

On midrange the tagMQMD includes ( at the end)

MQCHAR4 ApplOriginData; /* Application data relating to */

/* origin */

/* Ver:1 */

MQBYTE24 GroupId; /* Group identifier */

MQLONG MsgSeqNumber; /* Sequence number of logical message */

/* within group */

MQLONG Offset; /* Offset of data in physical message */

/* from start of logical message */

MQLONG MsgFlags; /* Message flags */

MQLONG OriginalLength; /* Length of original message */

/* Ver:2 */

on z/OS the tagMQMD has

MQCHAR4 ApplOriginData; /* Application data relating to */

/* origin */

/* Ver:1 */

and not the V2 fields.

If I use sizeof(MQMD) to compare the size is as expected ( good defensive coding practice) it does not match.

I am trying to port common code from midrange to z/PS

The common code has built an MQMD, with the extra fields, but it is larger than expected, and so the defensive checks detect this, and will not accept the MQMD.

It should be common code so I can port applications between midrange and z/OS.

Idea priority Medium
  • Admin
    Mark Taylor
    Jan 18, 2022

    Changing this on z/OS would have broken various compatibility requirements when the V2 MQMD was introduced. If you want to use the extended fields across platforms with no source code #ifdefs, then you can use the MQMD2 structure everywhere, or the MQMD (with or without being explicit about V1 as the distributed platforms still set the structure version to V1 by default) followed by an MQMDE. This is not something that will be changed.