Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Using the Criteria table
BMC AMI Utility Manager uses standard (Criteria table) criteria together with WHERE clause criteria to exclude or select objects for processing:
Order—The product checks the standard criteria before it checks WHERE clause criteria. If the standard criteria exclude an object, you can use the DO_WHERE function in the WHERE clause to select the object for processing. If the standard criteria select an object, you can use the SKIP_WHERE function in the WHERE clause to exclude it. For more information, see Reorg-criteria-column-checking-order.
Assume that the IBM RTS tables show base thresholds that would typically warrant reorganizing a table space and its index. Using BMC AMI Utility Manager, you could automatically apply criteria similar to the following examples.
The following example shows a TS_REORG_WHERE clause:
DO_WHERE (A.NACTIVE < 540 AND A.EXTENTS > 1)
In the next example, if the WHERE clause is true, BMC AMI Utility Manager reorganizes selected objects unless they have fewer than eight active pages. The example uses the WHERE clause only to exclude objects.
SKIP_WHERE (A.NACTIVE < 8)
The next example combines the WHERE clauses from the previous examples, selecting small objects that are in extents and excluding very small objects:
DO_WHERE(A.NACTIVE < 540 AND A.EXTENTS > 1) OR SKIP_WHERE(A.NACTIVE < 8)
This section provides information about the following topics:
