Default language.

Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Check for Db2 13.1.

Wildcards

Many keywords in BMC AMI Utilities use Db2 SQL wildcards to reference a series of similarly named objects. Use Db2 SQL wildcards precisely as you use them in a Db2 WHERE clause after the LIKE keyword. You can use any combination of characters, the percent character (%), or the underscore character (_) in either name.

In the simplest scenario, you would not use wildcards. The index creator and index name, and the database name and the table space name, are specified explicitly, without wildcards. To reorganize all the indexes with a specific creator ID, specify creatorID.%.

When you use masked names, BMC AMI Utilities construct and issue an SQL query to obtain the names of all indexes that match a specified naming mask.

The SYSPRINT and SUMMARY sections of the job listing print a line for each object found.

Example
REORG TABLESPACE APPL1.XXA%

This line generates one REORG TABLESPACE statement for every table space in the Db2 Catalog in database APPL1 whose table space name begins with the characters XXA.

Important

You can use wildcards with BMC AMI Reorg to specify objects in the Db2 catalog that you want to exclude from the reorganization.

Related topics

Overview-of-BMC-AMI-Utilities-concepts

Getting-started


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*