IBM Support

PI67394: BSDS DATASETS NOT CORRECT IF CLONING FROM SECONDARY MEMBERS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When we clone from secondary members of a data sharing group,
    the BSDS info passed to log apply is not correct. For example:
    
    If you have the following DS members:
    
    DATA-SHARING-MEMBERS(             -
      1,DBA5,DBA5PARM,                -
      2,DBB5,DBB5PARM                 -
    )                                 -
    
    and we ran on RS25 (where DBB5 resides). The BSDS entries
    in the FTRP block are set to:
    
    DBA5 DBA5PARM  DBB5.BSDS01 DBB5.BSDS02
    DBB5 DBB5PARM  DBB5.BSDS01 DBB5.BSDS02
    
    The entries for DBA5 should be  DBA5.BSDS01 DBA5.BSDS02.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When we clone from secondary members    *
    *                      of a data sharing group, the BSDS info  *
    *                      passed to log apply is not correct.     *
    *                      For example:                            *
    *                      If you have the following DS members:   *
    *                      DATA-SHARING-MEMBERS(             -     *
    *                        1,DBA5,DBA5PARM,                -     *
    *                        2,DBB5,DBB5PARM                 -     *
    *                      )                                 -     *
    *                                                              *
    *                      and we ran on RS25 (where DBB5          *
    *                      resides). The BSDS entries in the FTRP  *
    *                      block are set to:                       *
    *                      DBA5 DBA5PARM  DBB5.BSDS01 DBB5.BSDS02  *
    *                      DBB5 DBB5PARM  DBB5.BSDS01 DBB5.BSDS02  *
    *                                                              *
    *                      The entries for DBA5 should be          *
    *                      DBA5.BSDS01 DBA5.BSDS02.                *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI67394

  • 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

    2016-08-10

  • Closed date

    2016-08-31

  • Last modified date

    2016-10-03

  • 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 UI40536

       UP16/09/07 P F609

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:
03 October 2016