IBM Support

PM91546: PM53155 ( UK77362 / UK77363 / UK77364 ) PE FIX WITHOUT PM74803 ENABLEMENT FOR PM69760 13/06/20 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR is created to allow the customer to apply PE fix for
    PM53155 ( UK77362 / UK77363 / UK77364 ) without enabling APAR
    PM74803 code.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 for z/OS data sharing users with     *
    *                 PM53155 that need to apply its PE fixing     *
    *                 APAR PM77066 without applying enabling       *
    *                 APAR PM74803.                                *
    *                                                              *
    *                 PTFs for the above mentioned APARs:          *
    *                   PM53155 / UK77362 for DB2 10 for z/OS      *
    *                   PM53155 / UK77364 for DB2 9 for z/OS       *
    *                   PM53155 / UK77363 for DB2 V8 for z/OS      *
    *                                                              *
    *                   PM77066 / UK91321 for DB2 10 for z/OS      *
    *                   PM77066 / UK91323 for DB2 9 for z/OS       *
    *                   PM77066 / UK91322 for DB2 V8 for z/OS      *
    *                                                              *
    *                   PM74803 / UK90830 for DB2 10 for z/OS      *
    *                   PM74803 / UK90832 for DB2 9 for z/OS       *
    *                   PM74803 / UK90831 for DB2 V8 for z/OS      *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBHK ERQUAL500C *
    *                      during several data sharing members'    *
    *                      DB2 checkpoint after group restart,     *
    *                      leading to their DB2 crash with         *
    *                      MSGDSNV086E RC00D95001                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During group restart, while updating the group DBET in SCA,
    a subset of the DBET base SCA record(s) for an object was
    accidentally deleted, which resulted in local DBET entry for the
    object being built incorrectly.
    
    In this case, there were more than 200 partitions with diverse
    exception states such that the DBET entry for this object had
    multiple DBET blocks. During internal DBET rectify, at the
    beginning of forward log apply phase, the group DBET in SCA
    needed to be updated since local DBET had to reset an internal
    extend-in-progress state.
    
    However, when copying the local DBET blocks to the group DBET in
    SCA, by mistake not all the DBET blocks were copied. This
    resulted in an incomplete group DBET in SCA for this object.
    
    When other members of the data sharing group came up, their
    local DBET was built incorrectly, eventually leading to the
    aforementioned ABEND04E.
    
    The first member that performed the rectify was able to come
    up successfully because his local DBET was not corrupted. Any
    subsequent DBET updates that this member performed after the
    group restart automatically cleaned up the group DBET in SCA,
    which is why the originally failed members were able to restart
    on their second restart attempt.
    

Problem conclusion

  • DB2 code has been modified such that the group DBET in SCA is
    updated correctly during DBET rectify.
    
    Upcoming APAR, PM91547 will enable APAR PM69760.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM91546

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-20

  • Closed date

    2013-08-10

  • Last modified date

    2013-09-03

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

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

    UK96595 UK96596 UK96597

Modules/Macros

  • DSNIDBEL DSNIDBGN DSNIDBGR DSNIDBNG DSNIDBNI
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK96595

       UP13/08/16 P F308 ®

  • R810 PSY UK96597

       UP13/08/16 P F308 ®

  • R910 PSY UK96596

       UP13/08/16 P F308 ®

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 September 2013