IBM Support

PM76853: POSSIBLE CKZ02063E EXPLICIT TARGET DEVICE NUMBER NOT FOUND WHEN TARGET VOLUMES HAVE LOWEST DASD DEVICE NUMBERS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Possible CKZ02063E EXPLICIT TARGET DEVICE NUMBER NOT FOUND when
    the target volumes have the lowest DASD device numbers in the
    system.
    Also corrected:
    Possible CKZ02018E message when using COPY and FROM-VOLSER-DDN
    with large number of volumes
    Remove the limit in the COPY command on how many entries can be
    specified in FROM-VOLSER-DDN, TO-VOLSER-DDN, VOLPAIRS-DDN,
    VOLPAIRSDEVN-DDN, VOLPAIRSDEVN-NOCLIP-DDN, USERSGDEFS-DDN, and
    USERCATALOGS-DDN.
    

Local fix

  • For CKZ02063E a possible work around would be to move the target
    volumes with the lowest device numbers to higher device numbers.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *                 All users of IBM DB2 Cloning Tool for z/OS   *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1-                                      *
    *                      Possible CKZ02063E EXPLICIT TARGET      *
    *                      DEVICE NUMBER NOT FOUND when the        *
    *                      target volumes have the lowest DASD     *
    *                      device numbers in the system.           *
    *                                                              *
    *                      2-                                      *
    *                      Possible CKZ02018E message when using   *
    *                      COPY and FROM-VOLSER-DDN with large     *
    *                      number of volumes.                      *
    *                      Remove the limit in the COPY command    *
    *                      on how many entries can be specified in *
    *                      FROM-VOLSER-DDN, TO-VOLSER-DDN,         *
    *                      VOLPAIRS-DDN, VOLPAIRSDEVN-DDN,         *
    *                      VOLPAIRSDEVN-NOCLIP-DDN, USERSGDEFS-DDN *
    *                      and USERCATALOGS-DDN.                   *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76853

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-11-09

  • Closed date

    2012-11-26

  • Last modified date

    2012-12-04

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

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

Modules/Macros

  •    CKZ00246
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R310 PSY UK83725

       UP12/11/29 P F211

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]

Document Information

Modified date:
30 March 2021