PK58985: IDCAMS DELETE & RENAME STATEMENTS ORIGINALLY USED IN CASES WHEN NO OBJECTS EXIST ON TARGET. NOW ALSO OUTPUT IF DS DOES NOT EXIST

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• IDCAMS delete and rename statements originally pertained to
  situations when no objects exist on the target. Now they will
  also be output if the dataset doesn't exist. This could be due
  to DEFINE NO on the CREATE or for other reasons like the dataset
  is migrated or deleted inadvertently.
  Table space cloning now copies the source dataset(s) to the
  target using F0001 as the fifth level qualifier. SYNCDB2 output
  expects to find the target dataset (s) with F0001 and thus the
  target job should be run before executing the IDCAMS delete and
  rename statements.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 cloning tool.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: IDCAMS delete and rename statements     *
  *                      originally pertained to situations when *
  *                      no objects exist on the target. Now     *
  *                      they will also be output if the dataset *
  *                      doesn't exist. This could be due to     *
  *                      DEFINE NO on the CREATE or for other    *
  *                      reasons like the dataset is migrated    *
  *                      or deleted inadvertently.Table space    *
  *                      cloning now copies the                  *
  *                      source dataset(s)                       *
  *                      to the target using F0001 as the fifth  *
  *                      level qualifier. SYNCDB2 output expects *
  *                      to find the target dataset (s) with     *
  *                      F0001 and thus the target job should be *
  *                      run before executing the IDCAMS delete  *
  *                      and rename statements.                  *
  ****************************************************************
  * 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:

  UK33889

Modules/Macros

•    CKZ00246 CKZ00500 CKZ00501 CKZ00505 CKZ00506
  CKZ00510 CKZ00530 CKZ00532 CKZ00535 CKZ00536 CKZ00537 CKZ00538
  CKZ00544 CKZ00545 CKZ00546 CKZ00547 CKZ00548 CKZ00560 CKZ00561
  CKZ00562 CKZ00563 CKZ00564 CKZ00565 CKZ00566 CKZ00569 CKZ00573
  CKZ00600 CKZ00602 CKZ00611 CKZ00612 CKZ00613 CKZ00616 CKZ00624
  CKZ00625 CKZ00626 CKZ00627 CKZ00628 CKZ00629 CKZ00630 CKZ00631
  CKZ00632 CKZ00650 CKZ00651 CKZ00652 CKZ00653 CKZ00654 CKZ00655
  CKZ00670 CKZ00671 CKZ00672 CKZ00677 CKZ00678 CKZ00679 CKZ00727
  CKZ00728 CKZ00729 CKZ00730 CKZ00731 CKZ00732 CKZ00752 CKZ00753
  CKZ00754 CKZ00755 CKZ00760 CKZ00761 CKZ00762 CKZ00763 CKZ00770
  CKZ00778 CKZ00779 CKZ00780
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R210 PSY UK33889

     UP08/03/03 P F802

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.