PH64233: LOAD OF PBR TABLESPACE WITH FLASHCOPY USING ONE SYSREC TAKES FLASHCOPIES OF ALL THE PARTITIONS EVEN THE ONES NOT LOADED

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Customer runs LOAD LOG NO RESUME a PBR table at TABLESPACE level
  using only one SYSREC dataset.
  This LOAD uses a FCCOPYDDN to take Flashcopies.
  Several times the SYSREC dataset contains records for just one
  or a subset of partitions, so not all partitions are loaded.
  Result is that , even if only one partition is loaded from the
  SYSREC, then ALL the partitions are FLASHCOPIED
  There is no way for LOAD to just take a Flashcopy of the
  partitions being loaded and set COPYPENDING.
  

Local fix

• Run LOAD without flashcopy, this will set loaded partitions in
  COPY PENDING
  Then run a a separate COPY utilitywith FCCOPYDDN and SCOPE
  PENDING.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Db2 13 for z/OS LOAD LOG NO RESUME YES   *
  *                 FLASHCOPY utility users on a PBR table       *
  *                 space.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The LOAD LOG NO RESUME YES utility at   *
  *                      the table space level on a              *
  *                      partition-by-range table with           *
  *                      FLASHCOPY YES or CONSISTENT creates     *
  *                      copies of all partitions, even those    *
  *                      that did not have any records loaded.   *
  ****************************************************************
  For partition-by-range (PBR) table spaces, the current behavior
  of a table space level LOAD LOG NO RESUME YES FLASHCOPY
  operation is that a FlashCopy image copy (FCIC) is created for
  every partition in the table space, regardless of which
  partitions were actually loaded.
  
  With this APAR, the functionality has been improved so that a
  LOAD LOG NO RESUME YES FLASHCOPY utility invoked at the table
  space level now creates FCICs only for the partitions
  that were actually loaded.
  
  If the FlashCopy copy fails for the target object or auxiliary
  object and the LOAD statement includes LOG NO but not
  NOCOPYPEND, the table space is set to COPY-pending status. For
  partition-by-range table spaces, only the specific partitions
  that were loaded - and for which a FlashCopy image copy was
  attempted - are placed in COPY-pending status.
  
  This change is applicable to SHRLEVEL CHANGE and NONE for
  logged table spaces.
  

Problem conclusion

Temporary fix

Comments

• The LOAD LOG NO RESUME YES utility code has been modified to
  only take a FlashCopy of loaded partitions when run at the
  table space level for PBR table spaces. For this case, the
  behavior for FlashCopy image copies is now consistent with
  sequential inline image copy created by LOAD. The LOAD
  FLASHCOPY documentation has been changed to reflect this
  change.
  

APAR Information

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

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

  UO07489

Modules/Macros

• DSNURELD
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RD10 PSY UO07489

     UP26/04/22 P F604

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.