These are some questions which DB2 DBA's have in their life who are using Database Analyzer for DB2 for Z/OS.
Customers currently run PDA Statistics periodically and run RUNSTATS regularly this has become their schedule for years.
As a DBA you need to know about the health of your DB2 objects. However, does DB2 itself always need to know that your tables/indexes are getting disorganized?
PDA allows you to collect stats that only YOU can see and it will not impact DB2 Optimizer. Since IBM changes its DB2 Optimizer algorithm. We don't want customer to update DB2 catalog with PDASTATS as it may sometime adversely impact DB2 performance.
CA-Database Analyzer (PDA) catalog update – You can update catalog not related to DB2 Optimizer these statistics (non-optimizer a.k.a. space statistics) are 'primarily' used for object maintenance. All of these statistics are indeed collected by PDA and stored our history tables. These can easily be used to set thresholds/triggers to generate JCL which will perform object maintenance.