PM67183: DB2 OBJECT COMPARISON TOOL FOR Z/OS V10.1 DOES NOT GENERATE STOP COMMAND WHEN NEEDED DURING CHANGE MAXROWS SETTING FOR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 Object Comparison Tool for z/OS V10.1 does not generate STOP
  command when needed during change MAXROWS setting for
  TABLESPACE
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison           *
  *                 Tool for z/OS who compare table spaces       *
  *                 between source and target and alter          *
  *                 attributes MAXROWS, USING clause, ERASE,     *
  *                 and GBPCACHE that requires the table         *
  *                 space or partition to be in a stopped        *
  *                 state when the ALTER TABLESPACE statement    *
  *                 is executed.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DB2 Object Comparison Tool for      *
  *                      z/OS does not generate an explicit      *
  *                      STOP command in the APPLY jobs when     *
  *                      there is a table space attribute to     *
  *                      be altered that requires the table      *
  *                      space or partition to be in the         *
  *                      stopped state when the ALTER            *
  *                      TABLESPACE statement is executed.       *
  *                      Object Compare only generates the       *
  *                      ALTER statement for the change.         *
  *                      While running the APPLY jobs, the       *
  *                      Batch Restart program ADBTEP2 will      *
  *                      detect that the table space needs       *
  *                      to be stopped and run the STOP          *
  *                      command. The user is not aware of       *
  *                      this situation until run-time.          *
  *                                                              *
  *                      Here is an example:                     *
  *                                                              *
  *                      ALTER TABLESPACE MAXROWS                *
  *                      requires the table space be in          *
  *                      a stopped state in DB2 9 and prior      *
  *                      releases. During the APPLY, the ALTER   *
  *                      statement fails with a SQLCODE=-626 /   *
  *                      SQLCODEN626, and ADBTEP2 will issue     *
  *                      the command to stop the table space,    *
  *                      rerun the ALTER, then start the table   *
  *                      space after the ALTER is done.          *
  *                                                              *
  *                      ADB5044I *** INPUT STATEMENT:           *
  *                      ALTER TABLESPACE                        *
  *                      >dbname<.>tsname<  MAXROWS nn ;         *
  *                                                              *
  *                      ADB5125W SQLCODE= -626 returned         *
  *                      from ALTER.  A STOP will be issued      *
  *                      against the object.                     *
  *                                                              *
  *                      -STO DB(>dbname<) SPACE(>tsname<)       *
  *                                                              *
  *                      ADB5126I The previous ALTER is being    *
  *                      re-issued.                              *
  *                      ADB5178I RESULT OF SQL STATEMENT:       *
  *                      DSNT400I SQLCODE = 000,  SUCCESSFUL     *
  *                      EXECUTION                               *
  *                      ADB5180I SUCCESSFUL                     *
  *                      ADB5027I Object previously stopped.     *
  *                      A START will be attempted.              *
  *                      -STA DB(>dbname<) SPACE(>tsname<)       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The DB2 Object Comparison Tool for z/OS does not generate an
  explicit STOP command in the APPLY jobs when there is a table
  space attribute to be altered that requires the table space or
  partition to be in the stopped state when the ALTER TABLESPACE
  statement is executed. Object Compare only generates the ALTER
  statement for the change. While running the APPLY jobs, the
  Batch Restart program ADBTEP2 will detect that the table space
  needs to be stopped and run the STOP command.  The user is not
  aware of this situation until run-time.
  

Problem conclusion

• Problem has been resolved.
  According to the DB2 SQL Reference, altering the following
  table space attributes require the table space or partition
  to be in the stopped state on DB2 R810 and 9:
  
  MAXROWS, USING clause, ERASE, GBPCACHE.
  
  Altering the following table space attributes require the
  table space or partition to be in the stopped state on
  DB2 10:
  
  USING clause, ERASE, GBPCACHE.
  

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

•    ADBGAJOB ADBTEP2  ADB2CMF  ADB2CMR  ADB2WVL
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK90403

     UP12/12/19 P F212

• RA20 PSY UK90404

     UP12/12/20 P F212

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.