PI82382: CLONE USING TABLE NAME ON SOURCE AND TARGET INSTEAD OF TABLESPACE AND INDEXSPACE NAMES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This is information from the Customer:
  - Today they have two different data sharing groups (ex. DSG1
  and DSG2);
  - They want to clone a source table (BB.TABLE1) and all their
  indexes (IX1 and IX2) specifying just the BB.TABLE1 and the
  target table name from DSG1 to DSG2;
  - On the target the table name (BB.TABLE2) and the index
  names(IX3 and IX4 and IX5) may be different from the source;
  - Nowadays they have to list/match one by one the names of the
  objects on the source and the equivalent on the target defining
  the "pairs". They want to specify just the creator.table from
  source (BB.TABLE1) and from the target (BB.TABLE2) and the tool
  automatically identifies and match the indexes using their
  definitions (ex. IX1 = IX3). To perform that they coded a cobol
  program that navigate the DB2 catalog and lists all the indexes
  from source and target tables and compare/match their
  specifications.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM DB2 Cloning Tool z/OS.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: This is information from the Customer:  *
  *                      - Today they have two different data    *
  *                      sharing groups (ex. DSG1 and DSG2);     *
  *                      - They want to clone a source table     *
  *                      (BB.TABLE1) and all their indexes       *
  *                      (IX1 and IX2) specifying just the       *
  *                      BB.TABLE1 and the target table name     *
  *                      from DSG1 to DSG2;                      *
  *                      - On the target the table name          *
  *                      (BB.TABLE2) and the index names         *
  *                      (IX3 and IX4 and IX5) may be different  *
  *                      from the source;                        *
  *                      - Nowadays they have to list/match one  *
  *                      by one the names of the objects on the  *
  *                      source and the equivalent on the target *
  *                      defining the "pairs". They want to      *
  *                      specify just the creator.table from     *
  *                      source (BB.TABLE1) and from the target  *
  *                      (BB.TABLE2) and the tool automatically  *
  *                      identifies and match the indexes using  *
  *                      their definitions (ex. IX1 = IX3). To   *
  *                      perform that they coded a cobol         *
  *                      program that navigate the DB2 catalog   *
  *                      and lists all the indexes from source   *
  *                      and target tables and compare/match     *
  *                      their specifications.                   *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

•    CKZH494E
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R320 PSY UI48559

     UP17/07/08 P F707

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.