PI08607: DSNISGRT:0C2A PGEND WAS REPLACED BY IDMAP X'00' INCORRECTLY.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After DB2 is migrated to V10 NFM, data pages of UTS objects
  would be converted to new data page format to support pseudo
  delete function for data pages.
  
  If the UTS objects meet following conditions, PGEND of the data
  page could be replaced by IDMAP X'00' during INSERT.
  1. ROW LEVEL LOCKING.
  2. PGMAXID of the page is X'FF' before insert.
  3. data page is in old format before insert.
  
  If all conditions meet, INSERT might convert data pages and
  cause incorrect PGEND, which leads to DSNISGRT:0C2A abend and
  broken page.
  In DSN1PRNT output of broken page, you would see something like.
  --
  PGMAXID='00'X
  PGEND='.'
  ..
  RECORD:  XOFFSET='50FF'X
  ..
  7FE0 36E4352F 31320200 01D301A7 017B014F   012230F4 80008000
  49534806 47CB50FF
               ~~~~PGEND is replaced by offset of the new record
  inserted.
  --
  

Local fix

• REORG objects involved to convert all data pages to new V10 page
  format.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: DB2 10 NFM and DB2 11 for z/OS users of      *
  *                 universal table space (UTS).                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR addresses the following       *
  *                      problems during insert,                 *
  *                      1. ABEND04E RC00C90105 AT DSNISGRT      *
  *                         ERQUAL0C2A                           *
  *                      2. ABEND04E RC00C90105 AT DSNISGRT      *
  *                         ERQUAL0C27                           *
  *                      3. A record ID that is greater than the *
  *                         MAXROWS of the table space           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When following conditions are met during insert:
  1. DB2 is in V10 NFM or above,
  2. the target table space is UTS,
  3. the target page was not in V10 new format to support Pseudo
     Delete, and the insert converts it into V10 new format,
  4. PGMAXID of the target page was maxed out
  DB2 might assign PGMAXID + 1 as the ID for the new record on the
  page. So, if the maximum record IDs on one page is X'FF', the
  ID assigned for the new record would be wrapped to X'00', which
  is an invalid record ID. As a consequence, the forementioned
  ABENDs can occur. If the maximum IDs on one page is less than
  X'FF', the ID assigned could be invalid as well since it exceeds
  the MAXROWS specification of the table space.
  

Problem conclusion

• DB2 code has been modified to avoid assigning PGMAXID + 1 to the
  inserted record if PGMAXID has maxed out.
  

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:

  UI14689 UI14690

Modules/Macros

• DSNISGRT
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI14689

     UP14/02/18 P F402 ½

• RB10 PSY UI14690

     UP14/02/18 P F402 ½

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.