IBM Support

PH01997: OBJECTS WITH SAME SOURCE AND TARGET DATA SET NAME SHOULD NOT BE EXCLUDED FROM CLONING WHEN DATA-MOVER PGM(NONE) IS USED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When source and target objects have the same data set name, they
    are excluded from cloning. However, this is a valid scenario for
    cross-LPAR cloning when source and target LPARs do not have
    shared DASD or ICF catalogs. To properly support this scenario,
    Db2 Cloning Tool Tablespace Cloning should issue a warning
    message, but not exclude objects with same source and target
    data set names when DATA-MOVER PGM(NONE) is used.
    After applying this fix, Db2 Cloning Tool Tablespace Cloning
    issues a warning message, but does not exclude objects with
    same source and target data set names when DATA-MOVER PGM(NONE)
    is used.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM Db2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When source and target objects have     *
    *                      the same data set name, they are        *
    *                      excluded from cloning. However, this    *
    *                      is a valid scenario for cross-LPAR      *
    *                      cloning when source and target LPARs    *
    *                      do not have shared DASD or ICF          *
    *                      catalogs. To properly support this      *
    *                      scenario, Db2 Cloning Tool Tablespace   *
    *                      Cloning should issue a warning          *
    *                      message, but not exclude objects with   *
    *                      same source and target data set names   *
    *                      when DATA-MOVER PGM(NONE) is used.      *
    *                      After applying this fix, Db2 Cloning    *
    *                      Tool Tablespace Cloning issues a        *
    *                      warning message, but does not exclude   *
    *                      objects with same source and target     *
    *                      data set names when DATA-MOVER          *
    *                      PGM(NONE) is used.                      *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH01997

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-21

  • Closed date

    2018-09-11

  • Last modified date

    2018-10-02

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

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

Modules/Macros

  •    CKZ00620
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI58442

       UP18/09/14 P F809

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUUE","label":"IBM Db2 Cloning Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021