PI35991: SERVICEABILITY APAR FOR MODIFY UTILITY PROCESSING ABEND04E 00C90101 DSNIDBDF 5004 AND MULTIPLE DB2 MEMBER CRASH

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During MODIFY Utility processing ABEND04E RC00C90101 DSNIDBDF
  ERQUAL5004 was seen and multiple DB2 members crashed. This was
  because DB2 Plock/Notify exit engine ( 014.TLPLKNA9 ) found an
  invalid DBET entry for a large partitioned object, so the
  receiving members on processing the notify, abended.
  This is a serviceability apar to reduce the impact of
  the abend and add diagnostics.
   V11 apar PI38398
  Additional symptom: DSNIDBEL 5222 ERQUAL5222
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: DB2 10 for z/OS users running MODIFY         *
  *                 UTILITY                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND04E 00C90101 in DSNIDBDF 5004      *
  *                      when running MODIFY Utility.            *
  *                      Multiple DB2 members crashed.           *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When running the MODIFY Utility, the DBET gets out of sync
  and detects a problem with the local copy of the DBET when
  processing a notify exit.  This causes many of the data sharing
  members to abend and crash.
  When copying data to a member during a notify exit, a flag
  telling DBET that there is piece data was not accurately
  set.  This flag said that there was no piece data for this
  dbetdb and because of that, a copy of the data from the SCA
  was moved over data in the dbetdb that had piece data, making
  the piece data invalid.  This lead to an abend for inconsistent
  data and lead to the crash of several members.
  

Problem conclusion

• Servicablity is added to DBET code to check for inconsistencies
  in the DBET before issuing a notify to other members.  This
  limits the exposure of the problem to the originating member
  and keeps the other members from crashing with the same abend.
  Piece diagnostic information has been added to help with
  debugging.  Cleanup of piece information is now done when
  the piece storage is released so there is no residual states
  left in the DBET structure.
  To fix the problem with the invalid piece data flag, checking
  is done to make sure there is piece data before copying the
  data from the SCA to the member's dbetdb.
  

Temporary fix

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

Comments

APAR Information

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

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

  UI26836

Modules/Macros

•    DSNIDBAB DSNIDBBD DSNIDBDA DSNIDBDF DSNIDBDG
  DSNIDBDM DSNIDBDR DSNIDBDW DSNIDBEL DSNIDBFA DSNIDBGC DSNIDBGN
  DSNIDBHK DSNIDBIN DSNIDBMC DSNIDBMF DSNIDBMG DSNIDBMS DSNIDBNG
  DSNIDBNI DSNIDBPL DSNIDBPX DSNIDBSE DSNPXTN0 DSNWDFDM DSN1LDET
  DSN1LOUT
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI26836

     UP15/05/05 P F505 Ž

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.