IBM Support

PI45229: DDL TIMESTAMP MAY BE DUE TO IMPROPERLY FORMATTED LIMITKEY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DDL timestamp may be due to  improperly formatted limitkey
    Timestamps in limitkeys are stored without quotes in DB2
    versions before 11.
    
    Timestamps in limitkeys are stored in DB2 v11 with quotes.
    During the migration from a previous version to DB2 version 11
    timesamps in limitkeys are  saved without the quotes.
    
    DDL generation module will check quotes for timestamps in
    limitkeys and add them if they do not exist.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Cloning Tool for z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: DDL timestamp may be due to improperly  *
    *                      formatted limitkey Timestamps in        *
    *                      limitkeys are stored without quotes in  *
    *                      DB2 versions before 11. Timestamps in   *
    *                      limitkeys are stored in DB2 v11 with    *
    *                      quotes. During the migration from a     *
    *                      previous version to DB2 version 11      *
    *                      timesamps in limitkeys are  saved       *
    *                      without the quotes. DDL generation      *
    *                      module will check quotes for            *
    *                      timestamps in limitkeys and add them    *
    *                      if they 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

    PI45229

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-17

  • Closed date

    2015-10-26

  • Last modified date

    2015-12-08

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

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

    UI32364

Modules/Macros

  •    CKZFASM  CKZFCOMM CKZFDB2  CKZFLOG  CKZFMASK
    CKZFOBJX CKZFPIN  CKZFPMIB CKZFPSDP CKZFPTRN CKZFRAND CKZGASM2
    CKZGDB2  CKZGLOG2 CKZGOBJZ CKZGPDIB CKZZCOMM CKZZDB2  CKZZLOG
    CKZZMASK CKZZOBJX CKZZPIN  CKZZPTRN CKZZRAND CKZ00541 CKZ00547
    CKZ00562 CKZ00600 CKZ00611 CKZ00612 CKZ00644 CKZ00645 CKZ00646
    CKZ00647 CKZ00648 CKZ00671 CKZ00674 CKZ00712 CKZ00745 CKZ00746
    CKZ00747 CKZ00748 CKZ00767 CKZ00780 CKZ00782 CKZ00982 CKZ00990
    CKZ00991 CKZ00992
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R310 PSY UI32364

       UP15/10/29 P F510

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.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021