IBM Support

IV55911: WEBSPHERE MQ 7.1 OR 7.5, XMS C/C++ CLIENT APPLICATION CAN NOT MQGET BIGGER MESSAGE WHEN MQMD VERSION 1 IS USED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the Async Consume functionality, an XMS client is
    not able to retrieve large messages from WebSphere MQ Version
    7.1 or 7.5 queue managers. It seems that the XMS client always
    expects to retrieve a message with MQMD.Version 2, even if the
    customer does not specify it to be Version 2. The issue
    encountered is that messages are being returned with a Version 1
    on larger messages. Smaller messages are returned with a
    Version 2. This is a separate issue from the APAR IV53820.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of asynchronous consume who are using applications
    which require or expect a specific version level of the MQMD
    header for the messages returned to them. The XMS client is an
    example which supports version 2.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    When a multi-phase get was required internally to fetch a
    message, due to the need to increase the internal buffer size,
    the logic which ensures the MQMD returned is of the correct
    version was bypassed. Due to this code being bypassed, an MQMD
    could be provided to the client application which is not of
    the expected version.
    

Problem conclusion

  • The flow of execution has been altered to ensure that the
    logic responsible for setting the MQMD version is not bypassed.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.6
    v7.5       7.5.0.4
    
    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

    IV55911

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-26

  • Closed date

    2014-03-05

  • Last modified date

    2014-03-05

  • 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 AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R710 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1"}]

Document Information

Modified date:
01 October 2021