IBM Support

IT18248: MQ 7.5.0.7 AMS client MQGET or async consume fails but returns CompCode=MQCC_OK, Reason=MQRC_NONE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a certain scenario, the MQGET call returns incorrect results.
    
    The scenario is:
    - Advanced Message Security enabled.
    - Message is being browsed via client-side MQGET call, or
    server-side async consume.
    - MQGMO_CONVERT is included in the MQGMO.Options
    - Message is too large for the buffer supplied by the
    application.
    
    The expected outcome from this is CompCode=MQCC_FAILED,
    Reason=MQRC_TRUNCATED_MSG_FAILED.
    
    The actual outcome is CompCode=MQCC_OK, Reason=MQRC_NONE, which
    is the wrong outcome.
    
    This issue was introduced as an unintended side effect of the
    fix in IT14031.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of 7.5.0.7 queue managers with applications operating in
    the scenario described.  If in doubt, consider any 7.5.0.7 queue
    manager operating with Advanced Message Security to be
    potentially affected by this issue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an AMS-enabled async consume operation is browsing a
    message, it must internally use larger buffers to ensure the
    whole message is read and decrypted before data conversion is
    performed.  The internal logic MQ was using did not take account
    of the particular scenario described, and the successfully
    browsed-and-converted message was incorrectly passed to the
    application with a "success" return code.  In fact, it failed,
    because the application buffer was not big enough to receive the
    whole message.  The return codes should therefore have been
    CompCode=MQCC_FAILED, Reason=MQRC_TRUNCATED_MSG_FAILED.
    
    This issue was introduced as an unintended side effect of the
    fix in IT14031.
    

Problem conclusion

  • The design of the fix for IT14031 has been revised so that the
    correct return condition of CompCode=MQCC_FAILED,
    Reason=MQRC_TRUNCATED_MSG_FAILED is achieved.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.8
    
    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

    IT18248

  • 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-12-05

  • Closed date

    2017-01-31

  • Last modified date

    2017-09-22

  • 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:
22 September 2017