IBM Support

PI92517: CHECK-DATASET-COMPATIBILITY DOES NOT WORK WITHOUT SHARED DASD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • To check source and target data sets compatibility Cloning Tool
    invokes IDCAMS utility to obtain data set attributes and
    compares them. Currently IDCAMS is invoked on the source
    LPAR for source and target data sets both. If target data
    sets are not accessible from the source job then IDCAMS
    error occurs and wrong messages about data set attribute
    mismatches can appear. This fix allows to invoke IDCAMS
    utility for target data sets on the target LPAR from the
    TCPIP server job.
    

Local fix

  • Specify CHECK-DATASET-COMPATIBILITY(N)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: To check source and target data sets    *
    *                      compatibility Cloning Tool invokes      *
    *                      IDCAMS utility to obtain data set       *
    *                      attributes and compares them. Currently *
    *                      IDCAMS is invoked on the source LPAR    *
    *                      for source and target data sets both.   *
    *                      If target data sets are not accessible  *
    *                      from the source job then IDCAMS error   *
    *                      occurs and wrong messages about data    *
    *                      set attribute mismatches can appear.    *
    *                      This fix allows to invoke IDCAMS        *
    *                      utility for target data sets on the     *
    *                      target LPAR from the TCPIP server job.  *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI92517

  • 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-01-16

  • Closed date

    2018-01-29

  • Last modified date

    2018-02-01

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

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

Modules/Macros

  •    CKZ4RDLL
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI53522

       UP18/02/01 P F801

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:
01 February 2018