CA Tuesday Tip from Karina Pulink, Principal Support Engineer, for August 20 2013
Prior to Datacom version 12.0 only customers with the SQL option could access the Dynamic
System Tables (DST) data directly.
The addition of the AUTOCOLLECT feature removed that constraint.
To have the DST table data transferred to the AUTOCOLLECT SNAP database (DBID
1019), all that needs to be done is execute DBUTLTY with the following SYSIN :
AUTOCOLL OPTION=SNAPSHOT,MUFNAME=mufname
The MUFNAME= parameter needs to be a DBSYSID TARGET_MUF_LIST value.
You might have written your own user applications over the years to collect data
coming out of a PXX report at MUF EOJ for performance monitoring and tuning purposes .
The advantage of using SNAP database in place of the PXX report is that you
can filter out statistics or resources you are not interested in or focus on
selected resources. For example, you could have a query to report on just
the buffer usage statistics and another to report on any database area where
the EXCPs exceed a certain threshold, say 10000. Using Dataquery on-line or
batch instead of the PXX EOJ summary statistics report allows you to easily
view and evaluate the PXX summary data in many new and valuable ways.
If you want to retain statistics for future reference, executing the DBUTLTY
AUTOCOLL OPTION=DELTACRE results in the differences between two snapshots
being calculated and stored in database 1020. So for example, if a DBUTLTY
SNAPSHOT were scheduled to run at midnight each day, a DELTACRE would result
in the DELTA database containing statistics that show how much resource
activity occurred each day of the week.
The AUTOSCOPE User Guide explains the full capabilities of the AUTOCOLLECT feature
as well as the AUTOINFO and AUTOSTATS features as well.
See CA Datacom/DB 12.0 bookshelf
here (
https://support.ca.com/cadocs/7/CA%20Datacom%20DB%2012%200-ENU/Bookshelf.html )
See CA Datacom/DB 14.0 bookshelf
here (
https://support.ca.com/cadocs/7/CA%20Datacom%20DB%2014%200-ENU/Bookshelf.html )