PI87474: LOAD REPLACE SHRLEVEL REFERENCE DOES NOT LEAVE CHILD TABLE IN CHECK PENDING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A table with 2 parents was LOADED SHRLEVEL REFERENCE. All the
  data should have been discarded due to the RI CONSTRAINTS. But
  the data was loaded without any errors, warnings or restricted
  states despite the table being referentially corrupted. But,
  when the LOAD was run again without SHRLEVEL REFERENCE the
  job discarded all the rows and honored the ENFORCE CONSTRAINTS.
  A LOAD REPLACE SHRLEVEL REFERENCE w/o NOCHECKPEND specified
  should leave the target child table in check pending.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Db2 11 for z/OS and Db2 12 for z/OS      *
  *                 users of LOAD REPLACE SHRLEVEL REFERENCE     *
  ****************************************************************
  * PROBLEM DESCRIPTION: LOAD REPLACE SHRLEVEL REFERENCE into a  *
  *                      child table in a referential integrity  *
  *                      relationship did not leave the target   *
  *                      table space or partition in check       *
  *                      pending                                 *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  User ran a LOAD REPLACE SHRLEVEL REFERENCE, without NOCHECKPEND
  specified, into a dependent table of a referential integrity
  relationship.  The LOAD completed successfully, but the target
  table space or partitions were not put into check pending
  ( CHKP ) despite the fact that LOAD REPLACE SHRLEVEL REFERENCE
  did not enforce or check for RI and constraints.
  

Problem conclusion

• Code has been modified for LOAD REPLACE SHRLEVEL REFERENCE of
  a child table in a referential integrity relationship to set
  CHKP upon successful completion of the SWITCH phase.  However,
  LOAD with NOCHECKPEND specified would continue to honor the
  keyword and not set CHKP on the affected objects.
  Note:
  You cannot specify ENFORCE CONSTRAINTS with SHRLEVEL
  REFERENCE. If specified, DSNU124I is issued. If you specify
  SHRLEVEL REFERENCE, ENFORCE NO is used.
  

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:

  UI62505 UI62506

Modules/Macros

•    DSNUGCKP DSNUGSUG DSNUGSUU DSNUGUCA DSNULSWD
  DSNURUTB DSNURWBF DSNURWI
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI62506

     UP19/04/27 P F904

• RC10 PSY UI62505

     UP19/04/27 P F904

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.