PM21683: ABEND04E 00E20025 U=SYSOPR M=(N) C=810.DMC M=DSNTFRCV LOC=DSNIDBHK.DSNSVBK+09D0 10/09/06 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• PB72,ABND=04E-00E20005,U=SYSOPR  ,M=(N),C=810.SMC
  -DSNSFSTG,M=DSNTFRCV,LOC=DSNIDBHK.DSNSVBK +09D0
  
  Additional symptoms:
  04E 00E20005 RC00E20005 DSNSVBK OFFSET09D0
  04E 00E20029 RC00E20029 DSNSVBK OFFSET0A12
  04E 00E30081 RC00E30081 DSNTLIDE OFFSET0C9E
  04E 00C90101 RC00C90101 DSNIDBDF 5222 ERQUAL5222 VRACE5222
  db2ovrlay/K  smcoverlay
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 data-sharing users for z/OS V8 with  *
  *                 PK91699 / UK54451 applied and DB2 9 for      *
  *                 z/OS with PK91699 / UK54452 applied.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND04E RC00C90101                     *
  *                      LOC=DSNIDBHK.DSNSVBK+09D0 with PK91699  *
  *                      applied                                 *
  *                                                              *
  *                      ABEND04E RC00C90101 DSNIDBDF ERQUAL5222 *
  *                      with PK91699 applied                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an inconsistency with the internal DBET state extend-in-
  progress was detected between the notify message sending member
  (sender) and the notify message receiving member (receiver), the
  receiver abended with
  ABEND04E RC00C90101 LOC=DSNIDBHK.DSNSVBK+09D0 or
  ABEND04E RC00C90101 LOC=DSNIDM.DSNIDBDF:5222 and
  DB2 was brought down.
  
  The following abends could also be encountered:
   ABEND04E RC00E20029 DSNSVBK+0A12
   ABEND04E RC00E30081 DSNTLIDE+0C9E
  
  While trying to get the internal DBET state extend-in-progress
  back in synch among data-sharing members, the DBET SCA piece
  information was copied to a storage that had already been freed
  and re-used to store DBET piece control block.  As a result,
  the DBET SCA piece information overlaid the DBET piece control
  block.  The abend was encountered while trying to free the
  overlaid DBET piece control block.
  
  Another situation that resulted in the abend was that the DBET
  SCA piece information was not found in the SCA.
  

Problem conclusion

• DB2 was modified to get a separate storage that will be used
  to store the DBET SCA piece information when DBET tries to
  correct itself.
  
  DB2 was also modified to take out the return code checking from
  the read of SCA and tolerate the inconsistency at this point.
  DBET will try to correct itself later in the processing during
  housekeeping or cleanup.
  
  In addition, DB2 was also modified to correct the partition
  number used to create the DBET shadow piece block.
  
  Additional keywords: SMCOVERLAY
  

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:

  UK61376 UK61377

Modules/Macros

• DSNIDBDF
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R810 PSY UK61376

     UP10/11/02 P F011 ®

• R910 PSY UK61377

     UP10/11/02 P F011 ®

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.