PI96946: REORG TABLESPACE WITH LISTDEF GETS MSGDSNU3334I AFTER PROCESSINGAN EMPTY TABLESPACE WITH A DEFINE NO INDEX AND USES DB2SORT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• REORG TABLESPACE with LISTDEF externalizes error message:
  DSNU3334I REGION SIZE IS TOO SMALL. UTILITY CANNOT CONTINUE.
            INCREASE REGION BY xxxxK
  This happens after having processed an empty tablespace in the
  list that has a DEFINE NO index.
  The problem happens using DB2SORT as sort product. When using
  other sort product the problem does not occur.
  Additional Symptoms and Keywords:
  abend04E RC00E40045 in DSNUGSTB +194C
  abend878 or abendA78 in DSNUGBAC
  abend0C4 rc04 in CNKDSOP (Db2sort)
  abend0C9 in DSNUGBAC
  msgdsnu359I
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Db2 11 for z/OS and Db2 12 for z/OS      *
  *                 users of REORG TABLESPACE LIST using         *
  *                 DB2 Sort for z/OS.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: REORG TABLESPACE LIST failed with       *
  *                      MSGDSNU3334I REGION SIZE IS TOO SMALL   *
  *                      when processing multiple table spaces.  *
  *                      Failure occurred after an empty table   *
  *                      space with a DEFINE NO index was        *
  *                      processed and MSGDSNU359I KEYWORD       *
  *                      'SORTKEYS' SPECIFIED BUT NO INDEX OR    *
  *                      FOREIGN KEYS EXIST, KEYWORD IS IGNORED  *
  *                      was issued.                             *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  REORG TABLESPACE will start a data sort even for empty table
  spaces. However the index sort for this table space will be
  skipped if the index was created with DEFINE NO and was never
  materialized. However skipping the index sort led to an
  inconsistent state in the communication between the utility
  and Db2 Sort. Subsequent utility sorts picked up an incorrect
  amount of memory available to Db2 Sort and caused the utility
  failure.
  
  Additional keywords: DB2SORT/K DSNU3334I DSNU359I
  

Problem conclusion

• Code has been changed to correctly cleanup the Db2 Sort logic
  when skipping the index sort for undefined indexes.
  

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:

  UI55963 UI55964

Modules/Macros

•    DSNUGSRT
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI55964

     UP18/06/05 P F806

• RC10 PSY UI55963

     UP18/06/05 P F806

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.