Using the Product in a DB2 Environment › Background DB2 Catalog Extraction › Synchronous Data Gatherer › Summary of DB2 Customization Parameters

Summary of DB2 Customization Parameters

The DB2 parameters in TUNSSP00 are designed to be hierarchical in nature. The concept is that the administrator of CA Mainframe Application Tuner can determine the site’s preference for how the data should be collected.

Either of the following methods can be chosen:

• Sampling by using the standard sampling architecture
• Interception of data from DB2 by using the Harvester

The data collected with the Sampler is based only on active or waiting samples as the samples are taken during the monitor session. Therefore, you will see active and waiting sample percentages on the DB2 displays.

The data collected with the Harvester is based on statistics that are maintained and managed by the DB2 subsystem itself. This data includes (but is not limited to) such things as CPU time, counts of the times an SQL statement is executed, buffer counts, and so on.

Data can also be collected by both the Sampler and the Harvester at the same time.

The administrator can then decide if there is a need to see all static and dynamic SQL or if there is only interest in dynamic SQL and set the appropriate options listed in the section Synchronous Data Gatherer.

Next, the administrator can determine how granular the data needs to be. Is there a need for thread, or operator or location information? If so, set the appropriate options listed in the section Synchronous Data Gatherer.

Finally, if there is a need to have Explain information for either the sampled SQL, the harvested SQL, or both, set the appropriate Explain options listed in the section Synchronous Data Gatherer.

See the section Synchronous Data Gatherer for detailed information about each of these parameters.