PI67328: MODIFY USING LISTDEF PARTLEVEL DOES NOT DELETE SYSCOPY RECORDS WITH GDGLIMIT SPECIFIED

APAR status

• Closed as documentation error.

Error description

• MODIFY using a LISTDEF with PARTLEVEL was run. Image copies
  were at the table space level until the table space was
  converted to Partition By Growth ( PBG ), after which the image
  copies were at the partition level.  The GDGLIMIT option was not
  being honored, resulting in MSGDSNU577I and no SYSCOPY entries
  being deleted.
  

Local fix

• use an option other than GDGLIMIT
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
  *                 users of MODIFY RECOVERY utility.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: MODIFY RECOVERY RETAIN GDGLIMIT         *
  *                      utility against a partitioned table     *
  *                      space using DSNUM n did not delete      *
  *                      old SYSCOPY or SYSLGRNX records.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  User converted a table space from a nonpartitioned table space
  to a partitioned table space, then ran MODIFY RECOVERY RETAIN
  GDGLIMIT utility against this table space using DSNUM integer.
  MODIFY RECOVERY did not delete any SYSCOPY or SYSLGRNX records
  that were newer than the oldest recoverable point prior to the
  table space conversion.  The SYSCOPY and SYSLGRNX records were
  not deleted because there were image copies at the table space
  level that existed before the table space was converted.
  
  Use DSNUM ALL if image copies exist at the table space level
  prior to a table space conversion from a nonpartitioned to a
  partitioned table space.
  

Problem conclusion

• The DB2 Utility Guide under the MODIFY RECOVERY utility, under
  How MODIFY RECOVERY deletes row, has been modified similar to
  the following:
  
  Deletion of SYSLGRNX and SYSCOPY rows for a single partition
  or the entire table space.
  
  Use the following guidelines to determine whether to use DSNUM
  ALL or DSNUM integer:
  
  If image copies exist at table space level before the table
  space is converted from a nonpartitioned table space to
  a partitioned table space, like from a simple table space, or
  a single-table segmented (non-universal) table space to a
  partition-by-growth universal table space use  DSNUM ALL.
    Restriction: In this case, if you use DSNUM integer, MODIFY
    RECOVERY does not delete any SYSCOPY or SYSLGRNX records
    that are newer than the oldest recoverable point before
    table space conversion.
  

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:

  PI69069

Fix information

Applicable component levels