PM50942: ALT OF PQTY ONLY CAUSED DROP / CREATE INSTEAD OF ALTER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Administration Tool for z/OS a user enters ALT command to
  change only PQTY on a tablespace. This change caused DROP /
  CREATE scenario, when user was expecting an ALTER.
  .
  By running ALT in batch, it was discovered that there were two
  changes:  1. CREATOR and 2. PQTY.
  Joblog showed:
  .
  Compare tablespace source(uid1.tsname) and target(uid1.tsname)
       (D)Field CREATOR changed from SYSADM to uid2
       (A)Field PRIQTY changed from 720 to 1440
     Tablespace uid1.tsname will be dropped
     Tablespace will be recreated
  .
  Customer would like an ALTER only of PQTY without DROP/CREATE.
  

Local fix

• Edit job to add change in SQLID to CREATOR of the tablespace
  being modified. Add statement under //DDLIN DD as shown:
  .
  //DDLIN    DD *
  
  SET CURRENT SQLID='uid1';
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS with a different SQLID than the         *
  *                 CREATOR of a table space being altered.      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The customer used the Alter (ALT)       *
  *                      command to update the PRIQTY value for  *
  *                      a table space.  This change could       *
  *                      have been implemented by an ALTER       *
  *                      statement, but the customer's           *
  *                      SQLID was different from the            *
  *                      CREATOR of the table space, hence the   *
  *                      ALTER was replaced by a DROP/CREATE.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The customer used the ALT command to make a change to a table
  space that could be implemented by an ALTER statement, but
  the customer's SQLID was different from the CREATOR of the
  table space hence the ALTER was replaced by a DROP/CREATE.
  By running ALT in batch, it was discovered that there were two
  changes:  1. CREATOR and 2. PRIQTY.  The joblog showed:
  
  Compare tablespace source(uid1.tsname) and target(uid1.tsname)
       (D) Field CREATOR changed from SYSADM to uid2
       (A) Field PRIQTY changed from >old_priqty< to >new_priqty<
     Tablespace uid1.tsname will be dropped
     Tablespace will be recreated
  

Problem conclusion

• DB2 Object Compare will not compare the creator of a table
  space if the table space is dropped and recreated for a
  different reason than the difference in the CREATOR field, the
  table space will be recreated with the current (new) CREATOR.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

•    ADB2CMF
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK75982

     UP12/02/08 P F202

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.