LISTDEF processing against an object list containing some of the CA PTDB product objects fails indicating that the list contains no objects.
DSNU1008I - LISTDEF list-name CONTAINS NO OBJECTS
DSNU1001I - LISTDEF list-name CLAUSE IDENTIFIES NO NEW OBJECTS:
clause-type object-type object-qualifier.object-name
INCLUDE TABLESPACE PTDB.PDTDR150
INCLUDE TABLESPACE PTDB.PDTDT150
INCLUDE TABLESPACE PTDB.PDTET150
INCLUDE TABLESPACE PTDB.PSABP150
INCLUDE TABLESPACE PTDB.PSADB150
INCLUDE TABLESPACE PTDB.PSAVL150
INCLUDE TABLESPACE PTDB.PTSMATS1
INCLUDE TABLESPACE PTDB.PTSMATS2
DB2 version 10 or above.
Prior to Version 10, undefined objects were included in the list. However, beginning with Version 10, undefined objects (objects that have been created with DEFINE NO) are, by default, not included in the list.
The list of objects includes both redundant objects and undefined objects.
Specifically for the list of The PDT prefixed tablespaces (suffixed 150) were replaced as of release r16 with a new suffix of 160.
The PSA prefixed tablespaces (suffxed 150) were replaced as of release r16 with a new suffix of 160.
PLA tablespace PTSMAT1 was replaced by tablespace PTSMAT2 as of release r11.5. Tablespace PTSMATS2 is created as DEFINE NO intentionally. The tables within tablespace PTSMATS2 will not contain any data. These tables are used solely for templating purposes to issue SQL for the SMF Data Query functionality within Log Analyzer. Tablespace PTSMATS2 will therefore fail the LISTDEF listing as it is an undefined object (created with DEFINE NO).
Note, as of release r19 of the CA Database Management Solutions for DB2 for z/OS, a new DDL option has been introduced to enhance the post-installation and customization process. With the new SSDEFINE parameter in the SETUPxx PARMLIB member of CDBAPARM, you can now specify whether to create the underlying VSAM data sets for the product tablespaces and indexes when the product objects are created. The default is NO, the objects are not defined.
With regards to obsolete PTDB objects, you can use the procedure documented in Techdoc 551709 to identify all obsolete objects in your PTDB database.