PI79277: NEW USE-LAST-CONSISTENT-FLASHCOPY(Y/N) KEYWORD IN COPY COMMAND

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• These changes will allow users to use CONSISTENT FLASHCOPY data
  sets as source data sets for the following DATA-MOVER PGMs:
  NONE, ADDRDSSU, and EMCAPI. After the cloning CONSISTENT
  FLASHCOPY data sets from source to target in Source job Cloning
  Tool will do OBIDs translation and reset RBA for target data
  sets in Target job. This way will allow users to not stop Source
  objects and have consistent data on Target without the using of
  Log Apply. Also there is no limitations on the number of
  subtasks Cloning Tool can run concurrently on the Target job.
  .
  Cloning Tool will use the following logic:
  1) If USE-LAST-CONSISTENT-FLASHCOPY(Y) Cloning Tool will check
   that all objects which are cloned relates to any consistent
   FLASHCOPY.
  2) If some of tablespaces relate to another than the last
   consistent FLASHCOPY Cloning Tool will display warning that
   data can be inconsistent.
  3) If even one of tablespaces does not relate to any consistent
   FLASHCOPY Cloning Tool will not allow the cloning.
  4) If some indexspace of indexes with COPY YES has another
   PIT_RBA than related tablespace Cloning Tool will allow the
   cloning and set flag that REBUILD is required for such
   indexspace.
  5) If even one of indexspaces of indexes with COPY YES does not
   relate to any consistent FLASHCOPY and related tablespace is
   included to the cloning Cloning Tool will allow the cloning and
   set flag that REBUILD is required for such indexspace.
  6) If users clones indexes with COPY NO (e.g. XML indexes with
   COPY NO) Cloning Tool will allow the cloning and set flag that
   REBUILD is required for such indexes.
  7) Cloning Tool will use the names of consistent FLASHCOPY data
   sets as source data set names.
  8) Cloning Tool will check target data set names after the
   cloning in the target job because we can have data set names
   with data that do not match DB2 data sets naming convention.
   If Cloning Tool find such data sets IDCAMS will be used to
   rename those data sets.
  9) Cloning Tool will do object IDs translation and reset RBA for
   target data sets in Target job.
  10) Cloning Tool will not allow to use Log Apply with
   USE-LAST-CONSISTENT-FLASHCOPY(Y).
  11) Cloning Tool will not allow to use UNLOAD-LOAD with
   USE-LAST-CONSISTENT-FLASHCOPY(Y).
  .
  Requirement:
    The structure of data for objects in consistent FLASHCOPY
    should be the same as source objects structures.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM DB2 Cloning Tool z/OS.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: These changes will allow users to use   *
  *                      CONSISTENT FLASHCOPY data sets as       *
  *                      source data sets for the following      *
  *                      DATA-MOVER PGMs:                        *
  *                      NONE, ADDRDSSU, and EMCAPI. After the   *
  *                      cloning CONSISTENT FLASHCOPY data sets  *
  *                      from source to target in Source job     *
  *                      Cloning Tool will do OBIDs translation  *
  *                      and reset RBA for target data sets in   *
  *                      Target job. This way will allow users   *
  *                      to not stop Source objects and have     *
  *                      consistent data on Target without the   *
  *                      using of Log Apply. Also there is no    *
  *                      limitations on the number of subtasks   *
  *                      Cloning Tool can run concurrently on    *
  *                      the Target job.                         *
  *                      Cloning Tool will use the following log *
  *                      1. If USE-LAST-CONSISTENT-FLASHCOPY(Y)  *
  *                       Cloning Tool will check that all       *
  *                       objects which are cloned relates to    *
  *                       any consistent FLASHCOPY.              *
  *                      2. If some of tablespaces relate to     *
  *                       another than the last consistent       *
  *                       FLASHCOPY Cloning Tool will display    *
  *                       warning that  data can be inconsistent *
  *                      3. If even one of tablespaces does not  *
  *                       relate to any consistent FLASHCOPY     *
  *                       Cloning Tool will not allow the        *
  *                       cloning.                               *
  *                      4. If some indexspace of indexes with   *
  *                       COPY YES has another PIT_RBA than      *
  *                       related tablespace Cloning Tool will   *
  *                       allow the cloning and set flag that    *
  *                       REBUILD is required for such           *
  *                       indexspace.                            *
  *                      5. If even one of indexspaces of        *
  *                       indexes with COPY YES does not         *
  *                       relate to any consistent FLASHCOPY     *
  *                       and related tablespace is included to  *
  *                       the cloning Cloning Tool will allow    *
  *                       the cloning and set flag that REBUILD  *
  *                       required for such indexspace.          *
  *                      6. If users clones indexes with COPY    *
  *                       NO (e.g. XML indexes with COPY NO)     *
  *                       Cloning Tool will allow the cloning    *
  *                       and set flag that REBUILD is required  *
  *                       for such indexes.                      *
  *                      7. Cloning Tool will use the names of   *
  *                       consistent FLASHCOPY data sets as      *
  *                       source data set names.                 *
  *                      8. Cloning Tool will check target data  *
  *                       set names after the cloning in the     *
  *                       target job because we can have data    *
  *                       set names with data that do not match  *
  *                       DB2 data sets naming convention. If    *
  *                       Cloning Tool find such data sets       *
  *                       IDCAMS will be used to  rename those   *
  *                       data sets.                             *
  *                      9. Cloning Tool will do object IDs      *
  *                       translation and reset RBA for target   *
  *                       data sets in Target job.               *
  *                      10. Cloning Tool will not allow to use  *
  *                       Log Apply with                         *
  *                       USE-LAST-CONSISTENT-FLASHCOPY(Y).      *
  *                      11. Cloning Tool will not allow to use  *
  *                       UNLOAD-LOAD with                       *
  *                       USE-LAST-CONSISTENT-FLASHCOPY(Y).      *
  *                      Requirement:                            *
  *                        The structure of data for objects in  *
  *                        consistent FLASHCOPY should be the    *
  *                        same as source objects structures.    *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

Temporary fix

Comments

• APPLY the PTF.
  

APAR Information

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

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

  UI47025

Modules/Macros

•    CKZ$$PRM CKZBAKS  CKZBAKT  CKZBBKS  CKZBBKT
  CKZBCKS  CKZBCKT  CKZBTS   CKZHCOPC CKZHSETC CKZHTCOP CKZHTSET
  CKZH493I CKZJOBT3 CKZ00501 CKZ00510 CKZ00535 CKZ00536 CKZ00544
  CKZ00545 CKZ00546 CKZ00547 CKZ00554 CKZ00562 CKZ00600 CKZ00613
  CKZ00680 CKZ00709 CKZ00713 CKZ00715 CKZ1COPC CKZ1TCOP CKZ1TULD
  CKZ1ULDC CKZ2ADRD CKZ2BCLC CKZ2BDCJ CKZ2BLSJ CKZ2CLON CKZ2CMND
  CKZ2CMPN CKZ2COCP CKZ2COMM CKZ2CTCP CKZ2CULC CKZ2DALV CKZ2DAPS
  CKZ2DBSS CKZ2DB2A CKZ2DCCC CKZ2DCCH CKZ2DCRN CKZ2DDAT CKZ2DEFD
  CKZ2DFIX CKZ2DREN CKZ2DRFD CKZ2DSAP CKZ2DSCJ CKZ2DSCL CKZ2DSCN
  CKZ2DSCP CKZ2DSCS CKZ2DSQL CKZ2DSTP CKZ2DTCP CKZ2DTCS CKZ2EDAC
  CKZ2EDCV CKZ2EDDF CKZ2EDDL CKZ2EDDS CKZ2ELDC CKZ2EMCS CKZ2EMDC
  CKZ2ESCP CKZ2ETCP CKZ2FTSJ CKZ2GFSJ CKZ2GVAR CKZ2IVPL CKZ2JSKL
  CKZ2LACR CKZ2LAOP CKZ2LSTS CKZ2MAIN CKZ2MEPL CKZ2MSTF CKZ2MTMB
  CKZ2NPPR CKZ2OMRC CKZ2PDAC CKZ2PDBL CKZ2PJCI CKZ2PLAP CKZ2PLDC
  CKZ2PMDC CKZ2PRDM CKZ2PRFL CKZ2PRIM CKZ2PZPI CKZ2RTSC CKZ2SASV
  CKZ2SBCI CKZ2SCLT CKZ2SFRJ CKZ2SFSJ CKZ2SFTJ CKZ2SIDL CKZ2SJCI
  CKZ2SJCL CKZ2SJTS CKZ2SJTV CKZ2SKL  CKZ2SOMT CKZ2SOPR CKZ2SPCC
  CKZ2SPRF CKZ2SRNM CKZ2SRSV CKZ2SSCP CKZ2SSDS CKZ2SSID CKZ2SSLB
  CKZ2SSMC CKZ2SSSC CKZ2SSSJ CKZ2SSTM CKZ2SSTN CKZ2SSTS CKZ2SSTT
  CKZ2SSTV CKZ2STSS CKZ2TCOP CKZ2TDDC CKZ2TDDF CKZ2TDSP CKZ2TJCL
  CKZ2TRCF CKZ2TSCP CKZ2TSET CKZ2TTRN CKZ2ULCL CKZ2USET CKZ4ASYS
  CKZ4PROF CKZ4RDLL CKZ4TPRF CKZ49    CKZ6ADLL CKZ6BCPR CKZ6BLST
  CKZ6BOCL CKZ6BPDD CKZ6BSSP CKZ6BTCL CKZ6BTSS CKZ6DDFL CKZ6FIXC
  CKZ6GRPR CKZ6HLLS CKZ6IPRM CKZ6JBCD CKZ6JTLS CKZ6MAIN CKZ6OMRC
  CKZ6OPDD CKZ6OTLS CKZ6RPDD CKZ6SCPR CKZ6SPDD CKZ6SPRM CKZ6SQLC
  CKZ6SSPL CKZ6SSPR CKZ6STPC CKZ6STRT CKZ6TCPR CKZ6TPDD CKZ6TPRM
  CKZ6UPDC CKZ6UXCL CKZ8UTIL HCKZ320
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R320 PSY UI47025

     UP17/05/16 P F705

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.