PH24320: OBJECT COMPARE STOGROUP MASK/IGNORE GENERATES ALTER WITH NULL STOGROUP NAME UNEXPECTED TOKEN ADB2PA UNSUCCESSFUL PARSE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Object Compare where a mask or ignore is used for both source
  and target STOGROUPs may generate an ALTER with a null STOGROUP
  name. The compare report may indicate that this has happened
  with a message similar to the following:
  
  (A)Field USING STOGROUP changed from SYSDEFLT to ''
  
  Later in processing, when the ALTER is parsed and the
  USING STOGROUP clause has no name for the STOGROUP, the
  following error messages are generated:
  
  Unexpected token after STOGROUP keyword - expected storage group
   name
  
  ADB2PA: The following statement could not be parsed :
  
  ADMIN ALTER IMPLICIT LOB INDEX FOR TABLE >tablename<
  COLUMN(columname)
  PARTITION >partno< CLOSE NO USING STOGROUP
  
  Unsuccessful parse of DDL statement.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the Db2 Object Comparison Tool for  *
  *                 z/OS who specify that the STOGROUP for both  *
  *                 the source and target should not be taken    *
  *                 into account.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the STOGROUP of both the source    *
  *                      and target objects for a compare are    *
  *                      ignored or masked, compare may set the  *
  *                      STOGROUP to '', resulting in a parse    *
  *                      error during subsequent processing.     *
  ****************************************************************
  When the STOGROUP of both the source and target objects are to
  be ignored in the compare operation, the value may be set to
  '' (no value), which can cause the STOGROUP clause to be
  generated with no corresponding value.  This is syntactically
  invalid and results in a parse error.
  
  Example of typical error messages issued:
  
  Unexpected token after STOGROUP keyword - expected storage
  group name
  ADB2PA: The following statement could not be parsed:
  ADMIN ALTER IMPLICIT LOB INDEX FOR TABLE <table>
  COLUMN <column name> PARTITION <partno> USING STOGROUP
  Unsuccessful parse of DDL statement missing STOGROUP.
  
  With this fix applied, if Compare decides to set the STOGROUP
  value to " (none) for the target, the USING STOGROUP clause
  will not be generated.
  

Problem conclusion

• Problem has been resolved.
  

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:

  UI70852

Modules/Macros

• ADB2CME
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RC10 PSY UI70852

     UP20/09/01 P F008

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.