PM69806: LISTDEF EXCLUDE CLAUSE DOES NOT EXCLUDE DESIRED INDEXSPACES IN SOME CASES 13/02/19 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• when running listdef utility, exclude clause like this does not
  always exclude all objects expected:
  ...EXCLUDE INDEXSPACES INDEX myindex LOB RI
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS       *
  *                 USERS OF LISTDEF UTILITY WITH PM43441        *
  *                 APPLIED.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: LISTDEF EXCLUDE CLAUSE DOESN'T          *
  *                      PROPERLY EXCLUDE OBJECTS                *
  *                      FROM A LIST IN SOME CASES.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
    After applying PM43441 (PTF UK74045 in DB2 9, PTF UK74044 in
  DB2 10) EXCLUDE clauses in a list of objects defined by LISTDEF
  utility in some cases do not exclude the intended objects.
  This problem has been observed when the EXCLUDE clause
  specifies indexes or index spaces and features the filtering-
  type keywords RI, LOB, BASE, XML, or ALL, but could also
  occur for other object types.
    This problem was due to a logic error in list expansion
  code that was surfaced by the fix for PM43441.
    As a result, users may experience various symptoms stemming
  from utilities being run on objects unexpectedly (because they
  were not excluded from the LISTDEF), or the appearance of
  MSGDSNU1001I - CLAUSE IDENTIFIES NO NEW OBJECTS
  or other messages or indications that a LISTDEF has a different
  number of objects than expected.
  

Problem conclusion

•   Code was added to LISTDEF utility to properly process
  EXCLUDE clauses so that objects are correctly excluded as
  expected.
  

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:

  UK91693 UK91694

Modules/Macros

•    DSNUILSA
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK91693

     UP13/03/04 P F303

• R910 PSY UK91694

     UP13/03/04 P F303

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.