IBM Support

IJ12614: XMS .NET application doesn't honor header compression propertiesset in the application for unmanaged mode.

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

  • If header compression properties are set in the application, XMS
    .NET doesn't honor them in Unmanaged mode.
    The application doesn't throw any exception but the values set
    are simply ignored by XMS.
    
    If the properties are set in CCDT file and CCDT file is being
    used by the application,then XMS .NET applications honor these
    properties in unmanaged mode. Properties are ignored if set in
    the application
    

Local fix

  • CCDT can be used in Unmanaged mode.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    XMS .NET applications setting header compression properties in
    the application.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If the header compression properties XMSC.WMQ_HEADER_COMP &
    XMSC.WMQ_MSG_COMP are set in the application,XMS .NET ignores
    these two properties.These properties are supported in Unmanaged
    mode.
    The same properties work fine if CCDT file is used by the XMS
    .NET application.
    

Problem conclusion

  • If header compression properties are set in the XMS .NET
    application,then XMS .NET client should honor the properties in
    Unmanaged mode.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.12
    v9.0 LTS   9.0.0.7
    v9.1 LTS   9.1.0.3
    
    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

    IJ12614

  • Reported component name

    IBM MQ XMS V 8.

  • Reported component ID

    5724H7257

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-15

  • Closed date

    2019-04-05

  • Last modified date

    2019-04-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

    IBM MQ XMS V 8.

  • Fixed component ID

    5724H7257

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","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
05 April 2019