IBM Support

IT25580: Large message delivered to async consumer with incorrect CCSID specified in MQMD header

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 using the GMO_CONVERT option, an application receives a
    message larger than the original buffer length.  The message
    body has been converted, but the MQMD.CodedCharSetId reports the
    original CCSID before the message was converted.
    
    The application is using asynchronous consume directly, or is a
    Java/JMS application.
    .
    Additional keywords:
    MQGMO_CONVERT
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of client-connected applications which
    use async consume and request message conversion with
    MQGMO_CONVERT and messages larger than 4KB.
    
    This includes applications which use the MQ classes for JMS and
    MQ classes for Java, which implicitly use async consume to
    service  GET requests from applications.
    
    This issue is only seen when the converted message is larger
    than the unconverted messages, such as when converting from a
    single-byte to double-byte character set.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error when handling conversion of large messages within
    the MQ channel process (amqrmppa) meant that the MQMD prior to
    data conversion could be written into the returned data instead
    of the MQMD after conversion. As such the CCSID and encoding
    fields did not correctly reflect the converted data being
    returned.
    
    This logic error was injected by the code changes which address
    APAR IT14407 .
    

Problem conclusion

  • The MQ conversion logic has been corrected to return the MQMD
    fields reflecting the data after conversion.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.11
    v9.1 CD    9.1.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

    IT25580

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-04

  • Closed date

    2018-08-15

  • Last modified date

    2018-08-24

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

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

    PH01744

Fix information

  • Fixed component name

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
24 August 2018