How RUNSTATS is used in exception processing

This section explains how Db2 Automation Expert uses RUNSTATS in exception processing.

How Db2 Automation Expert determines the source of statistics when evaluating exceptions
The setting in the Use Stats From field determines the source of statistics used by Db2 Automation Expert when evaluating those conditions. The statistics can reside in the Db2 catalog (C in the Use Stats From field), the catalog history tables (H), a shadow catalog (S), the Db2 Automation Expert repository (R), or can be collected dynamically (U).
RUNSTATS and package set names
The selection of a particular Use Stats From value requires a corresponding package list name that was specified on the setup panel for Db2 Automation Expert.
How Db2 Automation Expert handles lack of RUNSTATS statistics
When retrieving RUNSTATS statistics from either the Db2 catalog, Db2 shadow catalog, history tables, or Db2 Automation Expert repository, Db2 Automation Expert verifies whether RUNSTATS has been run on an object prior to performing exception processing. If RUNSTATS statistics are not found, an error message is displayed and Db2 Automation Expert will attempt to continue processing.
How Db2 Automation Expert verifies whether RUNSTATS has been run on an object
Prior to performing exception processing, Db2 Automation Expert verifies whether RUNSTATS has been run on an object by checking the columns in certain tables.

Parent topic: Specifics about exception conditions