PH31836: CHECK DATA UTILITY: EXCEPTION TABLE ISSUES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ISSUE 1 - CHECK DATA utility requires a tablespace name when
  including an exception table - which becomes problematic,
  since Db2 V12 FL504 deprecated Non-UTS tablespaces.
  This means that only a single table can be defined per
  tablespace.
  Automation Tool should allow Db2 to create a new tablespace
  (and the related exception table) instead of creating a new
  exception table on an existing tablespace.
  ISSUE 2 - Program HAA@BSQL is not generating long table names
  correctly in the JCL.  This problem occurs when a tablespace,
  which contains a table with a long name (greater than 38 bytes),
  is specified for the )IF TABLE NAME NOT _EXISTS clause in the
  generated JCL.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: ISSUE 1 - CHECK DATA utility requires a *
  *                      tablespace name when including an       *
  *                      exception table - which becomes         *
  *                      problematic, since Db2 V12 FL504        *
  *                      deprecated Non-UTS tablespaces. This    *
  *                      means that only a single table can be   *
  *                      defined per tablespace.                 *
  *                                                              *
  *                      Automation Tool should allow Db2 to     *
  *                      create a new tablespace (and the        *
  *                      related exception table) instead of     *
  *                      creating a new exception table on       *
  *                      an existing tablespace.                 *
  *                                                              *
  *                      ISSUE 2 - Program HAA@BSQL is not       *
  *                      generating long table names correctly   *
  *                      in the JCL. This problem occurs when a  *
  *                      tablespace - which contains a table     *
  *                      with a long name (greater than 38       *
  *                      bytes) - is specified for the           *
  *                      )IF TABLE NAME NOT_EXISTS clause in     *
  *                      the generated JCL.                      *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  .
  

Problem conclusion

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

• HAA#IXP7 HAA$BUT2 HAA$BUTC HAA$BUTI HAA$BUTR HAA$BUTY HAA$DSFT
  HAA$UCHX HAAEXCTC HAAHUCHX
  

Fix information

• Fixed component name

  DB2 AUTOMATION

• Fixed component ID

  5697G6300

Applicable component levels

• R430 PSY UI73747

     UP21/02/04 P F102

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.