IBM Support

PK77105: CLONING TOOL DOES NOT CHECK THE DBET STATE BEFORE INITIATING THE COPY PROCESS WHICH THEN COMPLETES WITH RC=0

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Cloning Tool does not check the DBET state before initiating the
    COPY process which then completes with rc=0
    
    For each database on the source and target subsystem, a DISPLAY
    DATABASE command is now issued using ADVISORY and RESTRICT
    keywords chosen by the user or defaulted. This allow various
    utility status values to be detected and datasets related to the
    objects with these status values to be included or excluded from
    the copy operation.
    Objects with any of these status values are treated as
    mismatched.
    
    Thus, ALLOW-COPY-ON-MISMATCH determines if the datasets are to
    be copied or not.  For example any tables that have been altered
    such that the catalog column definitions do not match the page
    data are now detected and a warning issued that one or more
    objects are in AREO* status. A REORG should then be performed by
    the user before copying page data to the target subsystem. Note
    that AREO* status applies to be the source and target subsystem
    objects.  The catalog should match the page data on both
    subsystems. Failure to do the REORG may result in unusable
    datasets after the copy and target job execution.
    
    MR1104081220
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cloning Tool does not check the DBET    *
    *                      state before initiating the COPY        *
    *                      process which then completes with       *
    *                      rc=0. MR1104081220                      *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK77105

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-08

  • Closed date

    2009-02-16

  • Last modified date

    2009-03-03

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

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

    UK44078

Modules/Macros

  •    CKZ00501 CKZ00510 CKZ00536 CKZ00537 CKZ00544
    CKZ00547 CKZ00562 CKZ00564 CKZ00565 CKZ00600 CKZ00612 CKZ00780
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R210 PSY UK44078

       UP09/02/18 P F902

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":"2.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021