PI31178: LISTDEF WITH WILDCARD DOES NOT EXCLUDE LOB TABLESPACES IMPLICITELY CREATED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The customer has a LISTDEF statement that is including a set of
  tablespaces using the wildcard character ("*") and excluding
  a subset of them; among these tablespaces, there is a
  partitioned tablespace with a LOB column so also the respective
  LOB tablespaces are included as the LISTDEF uses the ALL
  specification.
  The LOB tablespaces were implicitely created by DB2 (SET CURRENT
  SQLRULES = STD).
  Later there is an EXCLUDE of this tablespace with ALL, so all
  the related LOB tablespaces should be excluded.
  This does not happen and there is a residual LOB tablespace
  included in the list when it shouldn't .
  

Local fix

• Include less object in the listdef .
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: ALL DB2 10 FOR z/OS AND DB2 11 FOR z/OS      *
  *                 users of LISTDEF utility.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A LISTDEF utility statement with an     *
  *                      EXCLUDE clause that specified the ALL   *
  *                      option did not exclude all of the       *
  *                      related LOB objects.                    *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available.         *
  ****************************************************************
  User used LISTDEF to define a list of objects similar to the
  following:
    LISTDEF mylist
      INCLUDE TABLESPACE DB1.TS2* ALL
      EXCLUDE TABLESPACE DB1.TS210 ALL
      EXCLUDE TABLESPACE DB1.TS215 ALL
      EXCLUDE TABLESPACE DB1.TS220 ALL
      EXCLUDE TABLESPACE DB1.TS230 ALL
  
  The resulting list included object DB1.TS230LOB which is one of
  the LOB table spaces of base table space DB1.TS230.  This LOB
  table space should be excluded according to the LISTDEF
  definition.
  
  The problem happens intermittently.  This problem might
  potentially be seen when other LISTDEF keywords are used, such
  as BASE, LOB or XML.
  

Problem conclusion

• LISTDEF utility was changed to handle the filtering keywords
  correctly.
  

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:

  UI24923 UI24924

Modules/Macros

•    DSNUILSA
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI24923

     UP15/02/28 P F502

• RB10 PSY UI24924

     UP15/02/28 P F502

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.