NGT Utility Manager maximizes application performance and saves resources by:
Enabling frequent reorganization executions (because the product can select fewer—or no—objects for processing)
Reorganizing only objects that match your reorganization criteria, thus preventing unnecessary reorganizations
The NGT Utility Manager product uses criteria that you specify and IBM DB2 runtime statistics (RTS) to identify database objects that require processing.
NGT Utility Manager identifies the table spaces and indexes for:
Copying with the Next Generation Technology Copy for DB2 for z/OS (NGT Copy) product
Reorganizing with the Next Generation Technology Reorg for DB2 for z/OS (NGT Reorg) product
Collecting statistics with the Next Generation Technology Stats for DB2 for z/OS (NGT Stats) product
Then, depending on the options that you select, NGT Utility Manager takes one of the following actions:
Identifies and reports the objects that require processing—but without actually processing them
Identifies objects that require processing and runs the appropriate NGT product to process the identified objects
To invoke NGT Utility Manager from the NGT Copy product, you must invoke
ACPMAIN—to drive your copies.
After setting up NGT Utility Manager, you can activate it by including an RTS keyword in your utility product's SYSIN statement.
In the following example, the RTS keyword invokes NGT Utility Manager to use real-time statistics to determine whether NGT Reorg should reorganize table space CENTRAL.%:
Using NGT Utility Manager to evaluate the objects before you process them offers the following advantages:
You can specify separate evaluation criteria for each object, or groups of objects.
NGT Utility Manager can recommend an index for reorganization even if the corresponding table space does not require reorganization.
NGT Utility Manager can trigger a reorganization even if the product has not initialized reorganization values in RTS.
You can use
WHEREclauses to specify custom criteria or conditions.
You can use the Schedule table to fine-tune when to run NGT products (for example, by forcing or preventing reorganizations for a particular day of the week, date, or date range).
You can use the Exceptions table to force or prevent reorganizations that deviate from the schedule defined in the Schedule table records.