IBM Support

PK20882: GOC COMPARE AGAINST DDL WITHOUT PRIQTY/SECQTY GETS MESSAGE 'TARGET PRIQTY=NNN IS KEPT' HOWEVER DDL HAS NO PRIQTY/SECQTY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DB2 Object Comparision tool generated DDL without a PRIQTY
    or SECQTY when the source did not contain a PRIQTY or SECQTY
    even though the product issued these messages:
     Field PRIQTY has not been specified on source (system default
     is used) target PRIQTY=nnn is kept
     Field SECQTY has not been specified on source (system
     default is used) target SECQTY=nnn is kept
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users  of DB2 Object Comparison Tool,        *
    *                 who compare table spaces with default        *
    *                 PRIQTY/SECQTY on source, are affected.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The  generated DDL without a PRIQTY or  *
    *                      SECQTY when the source did not contain  *
    *                      a PRIQTY or SECQTY,  had messages like  *
    *                      'TARGET PRIQTY=NNN IS KEPT' issued.     *
    *                      .*                                      *
    *                      At  catalog  compare  to  DDL  without  *
    *                      PRIQTY/SECQTY   resulted  in   message  *
    *                      "Field PRIQTY  has  not been specified  *
    *                      on  source  (system  default  is used)  *
    *                      target  PRIQTY=nnn is kept "  but  DDL  *
    *                      had no PRIQTY/SECQTY generated, if the  *
    *                      tablespace was dropped and recreated.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    See Problem Description.
    

Problem conclusion

  • The problem has been fixed by removing the message "Field PRIQTY
    has not been specified on source (system default is used) target
    PRIQTY=nnn is kept"  and  applying  the PRIQTY/SECQTY value from
    source (system default).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK20882

  • Reported component name

    DB2 OBJECT COMP

  • Reported component ID

    5697G6400

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-03-03

  • Closed date

    2006-07-10

  • Last modified date

    2006-08-02

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

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

    UK16375

Modules/Macros

  •    GOC2CMF
    

Fix information

  • Fixed component name

    DB2 OBJECT COMP

  • Fixed component ID

    5697G6400

Applicable component levels

  • R310 PSY UK16375

       UP06/07/22 P F607

  • R710 PSY UK16376

       UP06/07/22 P F607

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":"SSAUVH","label":"IBM Db2 Object Comparison Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021