IBM Support

PI22556: CFSTRUCT does not disconnect when expected, and remains active after a checkpoint, when it has been inactive >10 minutes.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • During a checkpoint, the queue manager should
    disconnect from a CF Structure as it has not
    been used in over 10 minutes, but due to the
    strb_in_use_count being higher than expected
    this does not occur.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: During checkpoint processing, the queue *
    *                      manager does not successfully           *
    *                      disconnect from CF structures that have *
    *                      not had an open object using it for     *
    *                      over 10 minutes prior to the            *
    *                      checkpoint.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When opening a object on a structure that is already connected
    to the queue manager, a flag is set and a connection is not
    attempted. The strb_in_use_count is also incremented early on in
    the processing. In the case where an error occurs during the
    open processing, in CSQEOPEN, the processing will not complete
    successfully but will not decrement the count, causing the count
    to be inconsistent. An example of an error occurring during the
    processing includes the object being deleted, causing the object
    not to be present in DB2.
    
    The count of open objects is inconsistent, which will result in
    the structure not disconnecting when expected, or errors in the
    close processing of the structure. The primary case is when the
    structure has not been used by any open objects for over 10
    minutes and a checkpoint is taken, which should result in the
    structure being disconnected, but in this scenario this does not
    occur.
    

Problem conclusion

Temporary fix

Comments

  • The code was changed to keep the count of open objects
    consistent, correcting the reported issues.
    

APAR Information

  • APAR number

    PI22556

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-23

  • Closed date

    2014-08-22

  • Last modified date

    2014-11-04

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

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

    UI20811

Modules/Macros

  • CSQEOPEN
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI20811

       UP14/10/02 P F410

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

Document Information

Modified date:
04 November 2014