IBM Support

PI99195: CHECK-DATASET-COMPATIBILITY FAILS DURING IDCAMS LISTCAT PROCESSING WHEN SOURCE OBJ HAS MORE EXTENSIONS THAN TARGET OBJ

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Before applying this fix, CHECK-DATASET-COMPATIBILITY fails
    during IDCAMS LISTCAT processing when the number of source
    object extensions is greater than the number of target
    object extensions. Translated source data set names are sent
    to IDCAMS LISTCAT for compatibility checking, but the target
    data sets do not exist, which leads to a LISTCAT error.
    After applying this fix, Db2 Cloning Tool Table Space Cloning
    does not send to IDCAMS translated names for target data sets
    that do not exist.
    

Local fix

  • Turn off CHECK-DATASET-COMPATIBILITY or define target data sets
    manually
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM Db2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Before applying this fix,               *
    *                      CHECK-DATASET-COMPATIBILITY fails       *
    *                      during IDCAMS LISTCAT processing when   *
    *                      the number of source object extensions  *
    *                      is greater than the number of target    *
    *                      object extensions. Translated source    *
    *                      data set names are sent to IDCAMS       *
    *                      LISTCAT for compatibility checking,     *
    *                      but the target data sets do not exist,  *
    *                      which leads to a LISTCAT error.         *
    *                      After applying this fix, Db2 Cloning    *
    *                      Tool Table Space Cloning does not send  *
    *                      to IDCAMS translated names for target   *
    *                      data sets that do not exist.            *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI99195

  • 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-06-14

  • Closed date

    2018-08-07

  • Last modified date

    2018-09-04

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

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

Modules/Macros

  •    CKZWFCPY
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI57740

       UP18/08/10 P F808

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:
04 September 2018