IBM Support

PI18328: WMQ - CLIENT CHANNELS MAY HANG AFTER AN ABEND5C6-00E2000B DUE TO A LACK OF STORAGE IN MSTR ADDRESS SPACE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An instance of client channel was in the middle of publishing
    to a TOPIC when a 5C6-00E2000B occurred due to a lack of
    storage in the queue-manager address space.
    At the time of the abend it was holding a read mutex on the
    topic node, but recovery processing did not release the lock.
    This then caused client channels to hang during termination
    processing when they tried to get a write mutex on the topic
    node, and was the reason that the queue-manager needed to be
    FORCE'd.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Publish subscribe applications hang     *
    *                      when publishing, subscribing or         *
    *                      terminating following an earlier abend  *
    *                      of a publishing application.            *
    *                      In some cases this can cause the        *
    *                      channel initiator and/or queue manager  *
    *                      to hang during shutdown processing.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application publishing to a topic abended while holding a
    mutex on the topic node, and the subscription that was being
    delivered to.
    Recovery processing did not release the mutexes, which remain
    held until the abending application terminates.
    Any application requiring a write mutex on the same topic or
    subscription hang waiting for these mutexes to be released.
    

Problem conclusion

  • CSQMTPUT is changed to release any topic node and subscriber
    mutexes it holds during recovery processing.
    010Y
    100Y
    CSQMTPUT
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI18328

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-05-21

  • Closed date

    2014-07-30

  • Last modified date

    2014-09-03

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

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

    UI20094 UI20095

Modules/Macros

  • CSQMTPUT
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UI20094

       UP14/08/30 P F408 ¢

  • R100 PSY UI20095

       UP14/08/30 P F408 ¢

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 September 2014