Creating exception profiles

Exception profiles allow you to define when a utility in a utility profile is to be run against an object in an object profile.

For example, you might define an exception to examine the PERCDROP column in SYSTABLEPART (which contains the percentage of space that is occupied by rows of dropped tables). If you specify a comparator and value of "greater than 10", you can define the job profile such that a REORG might be triggered for those objects with more than 10% space occupied by dropped table rows.

After you select exception conditions, you can edit and customize the exceptions logic to control how exception processing evaluates multiple exception conditions. For example, you can add parentheses around exception conditions to group those exceptions into a logical set of conditions that are evaluated as an overall AND or OR.

Exception profiles are placed in the job profile with at least one object and one utility profile. During the job build, the exception criteria are processed and produce a list of accepted objects (those that meet the conditions) and a list of rejected objects (those that do not meet the conditions). You can specify whether the utility is to be run on the accepted objects, the rejected objects, or both, in the utility profile.

Db2 Automation Expert offers various exceptions conditions that you can specify in a profile. For example, DSNACCOX-like exception conditions simulate the results of the DSNACCOX stored procedure that is provided with Db2. You can use these exceptions to get recommendations for when to reorganize or image copy objects, or to update statistics for table spaces or index spaces.

In addition, you can incorporate user exits to allow extension of Db2 Automation Expert exception monitoring beyond its native z/OS® environment.

Through the Exceptions Profile Display, you can also access the Db2 Automation Expert statistics reporting and maintenance facility.