IBM Support

IT19363: MQOUTPUT DOES NOT SET THE MQMD.FORMAT FIELD CORRECTLY WHEN GENERATING AN MQMD FOR MESSAGE TREE THAT HAS OTHER MQ HEADERS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When a message tree propagated to an MQOutput node does not have
    an MQMD folder, then an MQMD is generated. The rest of the
    message tree is processed to determine the CodedCharSetId,
    Encoding and the Format fields that should be set in the
    generated MQMD. If the message tree contains other MQ headers
    then the Format name is not set correctly to reflect the first
    MQ header. If this MQ message is processed by any other
    application then the MQRFH2 will not be identified.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10.0 MQOuput nodes.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a message is propagated to an MQOutput node an MQPUT is
    issued to the queue(s) specified. To do this an MQMD is
    populated from the message tree's MQMD folder. If the message
    tree does not have an MQMD folder then an MQMD is generated. The
    rest of the message tree is processed to determine the
    CodedCharSetId, Encoding and the Format fields that should be
    set in the generated MQMD.
    
    If the message tree contains other MQ headers then the Format
    name is not set correctly to reflect the first MQ header. As
    such, if this MQ message is processed by any other application
    then the MQRFH2 will not be identified.
    
    For example, if the output message is parsed by another IBM
    Integration Bus message flow, a BIP5004/BIP5009 exception would
    be thrown for an XML message because the MQRFH2 bytes would be
    treated as XML.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT19363

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-22

  • Closed date

    2017-05-25

  • Last modified date

    2017-05-25

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020