IBM Support

IT13736: Messages put with a RFH2 header are being corrupted when retrieved when the message has an invalid MQMD format field.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using MQ 7.5.0.5, when a message with an RFH2 and invalid MQMD
    Format fields are used, if a message is put with a RFH2 header
    the message contains invalid characters in the RFH2 when the
    message is retrieved.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of MQ who are putting messages with an
    MQMD format field which is null padded, and are using RFH2
    headers.
    
    MQ specifies that the MQMD format field must be blank (space)
    padded.
    
    All Users of Message Broker V8.0 and IBM Integration Bus V9.0
    using an MQ Output node are affected due to APAR IT13853.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    MQ APAR IT02389 (included in MQ 7.5.0.5) introduced changes to
    RFH2 processing, which result in this issue if an invalid format
    field is encountered. It is expected that the format field in
    the header preceding an RFH2 header should be set to "MQHRF2  "
    (note the 2 spaces), however if this was set to
    "MQHRF2<null><null>" then the queue manager did not correctly
    store the RFH2, which lead to incorrect characters being
    inserted when the header was reattached to the message on a GET.
    

Problem conclusion

  • The application behaviour should be corrected to permanently
    resolve this issue. Users of Message Broker V8.0 and IBM
    Integration Bus V9.0 should accordingly apply APAR IT13853 to
    any installations which use an MQ Output node.
    
    
    As a temporary remediation, this APAR adds a new environment
    variable, AMQ_PARTIAL_MATCH_RFH2. If this variable is set to any
    value in the environment used to start the queue manager, then
    only the first 6 characters of the format field are considered
    when checking if the format is MQHRF2.
    
    If using this variable, it must be set before the messages are
    put to the queue in order to take effect.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.8
    v8.0       8.0.0.6
    v9.0 CD    9.0.2
    v9.0 LTS   9.0.0.1
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT13736

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-11

  • Closed date

    2016-11-30

  • Last modified date

    2017-06-01

  • 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

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 June 2017