IBM Support

PI78639: SPLIT THE UNLOAD/LOAD PROCESS BETWEEN SOURCE AND TARGET JOBS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Users normally use DATA-MOVER PGM(NONE) when cloning objects
    between different LPARs without shared DASD. Currently DB2
    Cloning Tool does not support UNLOAD/LOAD processing with
    DATA-MOVER PGM(NONE). This enhancement will split the
    UNLOAD/LOAD process between Source and Target jobs to allow
    UNLOAD/LOAD to be used with DATA-MOVER PGM(NONE).
    DB2 Cloning Tool will call UNLOAD in Source job and LOAD
    in Target job.
    Also, this enhancement allows users to use data masking with
    UNLOAD/LOAD functionality.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Users normally use DATA-MOVER PGM(NONE) *
    *                      when cloning objects between different  *
    *                      LPARs without shared DASD. Currently    *
    *                      DB2 Cloning Tool does not support       *
    *                      UNLOAD/LOAD processing with             *
    *                      DATA-MOVER PGM(NONE). This enhancement  *
    *                      will split the UNLOAD/LOAD process      *
    *                      between Source and Target jobs to       *
    *                      allow UNLOAD/LOAD to be used with       *
    *                      DATA-MOVER PGM(NONE). DB2 Cloning Tool  *
    *                      will call UNLOAD in Source job and      *
    *                      LOAD in Target job.                     *
    *                      Also, this enhancement allows users to  *
    *                      use data masking with UNLOAD/LOAD       *
    *                      functionality.                          *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI78639

  • 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

    2017-03-22

  • Closed date

    2017-04-17

  • Last modified date

    2017-05-01

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

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

Modules/Macros

  •    CKZ2MAIN
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI46483

       UP17/04/24 P F704

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