PI65766: ABEND 04E-00E40106,DSNUCALZ+36C4

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ABEND=04E REASON=X'00E40106' CAUSE=X'00C9000A' in DSNUCALZ+36C4
  of COPY INDEXSPACE with FLASHCOPY CONSISTENT options.
  During the recovery process, the shadow pageset of the index was
  treated as partitioned pagesets instead of a linear pageset,in
  such a case, when the "previous leaf's page number" of an index
  page be compared to the range of the "partition" instead of the
  whole linear dataset at the range check. The number beyond the
  "issue" range thus ABEND.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 V10 for z/OS and DB2 V11 for z/OS    *
  *                 users of COPY and RECOVER utilities with     *
  *                 FLASHCOPY CONSISTENT options.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: COPY FLASHCOPY CONSISTENT on an index   *
  *                      of a non-partitioned table space        *
  *                      abended with ABEND04E RC00E40106 and    *
  *                      RC00C9000A at DSNUCALZ OFFSET36C4 in    *
  *                      the LOGAPPLY phase.                     *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available.         *
  ****************************************************************
  A COPY SHRLEVEL CHANGE with FLASHCOPY CONSISTENT options ran on
  an index of a non-partitioned table space.  The index had
  multiple pieces.  The COPY utility abended with ABEND04E
  RC00E40106 and RC00C9000A at DSNUCALZ + '36C4'x during the
  LOGAPPLY phase, because the previous page of an index leaf page
  was incorrectly detected as out of the page range of its
  partition.
  This problem occurred because the FlashCopy of the
  non-partitioned index was opened as a partitioned pageset for
  log apply of the COPY utility, so the index was incorrectly
  treated as partitioned in some sanity check of the index page.
  The same problem can happen in other operations of index log
  apply in COPY and RECOVER with FLASHCOPY CONSISTENT.
  
  Additional Keywords: PRELOGA phase of RECOVER
  

Problem conclusion

• Index Manager code has been modified to check if the index is
  defined as partitioned index for COPY and RECOVER utilities with
  FLASHCOPY CONSISTENT options.
  

Temporary fix

Comments

APAR Information

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

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

  UI41173 UI41178

Modules/Macros

• DSNKCHKP DSNKDLE  DSNKIXDB DSNKLTCH DSNKPEXT
  DSNKPLOK DSNKTRAV DSNKULTH DSNKUNR2
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI41178

     UP16/10/25 P F610

• RB10 PSY UI41173

     UP16/10/25 P F610

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.