IBM Support

PI68172: MQ V800 - HIGH CPU CONSUMPTION IN MODULE CSQLLPLM.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • High CPU consumption in module CSQLLPLM.
    
    It occurs when an application browses messages on the queue,
    and then closes the queue with the delete-purge option. The
    IS allocation page lock that browse processing obtained prior
    to the close of the queue is not released, causing the problem
    seen with high CPU in CSQLLPLM.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: High CPU in load module CSQLLPLM due to *
    *                      a build up of allocation locks on pages *
    *                      used by dynamic queues.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When browsing a dynamic queue, an application obtained an
    allocation lock on the pages currently under the browse cursor.
    When the application closed the queue it specified that the
    dynamic queue should be deleted (e.g. passing MQCO_DELETE_PURGE
    to MQCLOSE), and so CSQMCLS2 called CSQIDDEL to delete the
    queue. When this returned CSQMCLS2 called CSQIMBLR to release
    the locks under the browse cursor, however because the IVSA for
    the queue no longer existed CSQIMBLR could not determine if the
    queue was private or shared, and so skipped releasing the locks.
    
    Over time the number of allocation locks that had not been
    correctly released by a long running application can build up,
    leading to high CPU in CSQLLPLM while searching long chains of
    lock control blocks.
    

Problem conclusion

  • CSQIMBLR is changed to correctly release the allocation locks
    when called as part of a close operation that also deletes the
    dynamic queue.
    000Y
    CSQIMBLR
    CSQMCLS2
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI68172

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-26

  • Closed date

    2016-09-26

  • Last modified date

    2016-11-02

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

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

    PI68940 UI41080

Modules/Macros

  • CSQIMBLR CSQMCLS2
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI41080

       UP16/10/06 P F610 ¢

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"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":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 November 2016