Default language.

Limited supportBMC 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 Utility Manager for Db2 13.1.

Utility Manager option description

This topic describes the Utility Manager options:

Keyword

Explanation

ngtUtilityStatement

Specifies the utility for which you want to evaluate objects (for example, REORG to run an evaluation for BMC AMI Reorg, or COPY for BMC AMI Copy).

RTS

Triggers BMC AMI Utility Manager to check the Exceptions, Criteria, Schedule, and Duration tables to determine whether to run the specified BMC AMI Utility.

Examples
 //SYSIN DD *
  REORG TABLESPACE WORKDB.INV% RTS
 //SYSIN DD *
  COPY TABLESPACE CENTRAL.ACCT% RTS
 //SYSIN DD *
  RUNSTATS TABLESPACE CENTRAL.ACCT% RTS
 //SYSIN DD *
  NGTSTATS TABLESPACE CENTRAL.ACCT% RTS

appCriteriaRecord

Specifies the NAME field in a TYPE=AP criterion record.

When specified, BMC AMI Utility Manager processes the object against the named criterion record for the specified application.

Examples

The following example specifies an application-specific record for a utility run:

//SYSIN DD *
  RUNSTATS TABLESPACE CENTRAL.ACCTMSTR RTS(ACCOUNTING)

In the following statement, the product processes against the named criterion record for application CRIT001:

REORG TABLESPACE MEDRECS.PATIENTS RTS(CRIT001)

REPORTONLY

Tells BMC AMI Utility Manager to report which objects should be processed, without processing them.

BMC AMI Utility Manager expands the statement object (which can be a wildcard pattern) and analyzes it against the criteria in the Exceptions and Criteria tables. BMC AMI Utility Manager then generates a report (see Sample summary report) that lists the objects that would have been processed or skipped.

Processing accesses only BMC AMI Utility Manager and DB2 Real Time Stats tables (no user tables).  

Important

REPORTONLY tells BMC AMI Utility Manager to analyze the statement object against the criteria in the Exceptions and Criteria tables only; REPORTALLperforms the same action against the Exceptions, Criteria, and Schedule tables.

Example

This example generates an BMC AMI Utility Manager report while excluding the objects from processing:

//SYSIN DD *
  REORG OBJECTSET PROD.ACCOUNTING RTS(,REPORTONLY)

Sample summary report

-- BMC Next Generation Technology   V vv.rr.mm

RTS REORG EXCLUDED TABLESPACE REPORT (STATEMENT 1)               
DATABASE  TABLESPACE             EXCLUDE                         
NAME      NAME        PART(S)    REASON                          
--------  ----------  ---------  --------------------------------
DSN8DCAT  ABC         0001       EMPTY_TABLESPACE       
DSN8DCAT  ABC         0002:0004  PASSED ALL RTS CRITERIA

RTS REORG EXCLUDED INDEX REPORT (STATEMENT 1)             
INDEX               INDEX                          EXCLUDE
CREATOR             NAME                PART(S)    REASON
------------------  ------------------  ---------  -----------------------
DSN8DCAT            ABCX1               0001:0004  PASSED ALL RTS CRITERIA

REPORTALL (PTF BQU1353 applied)


Tells BMC AMI Utility Manager to report which objects should be processed, without processing them

BMC AMI Utility Manager expands the statement object (which can be a wildcard pattern) and analyzes it against the criteria in the Exceptions, Criteria, Schedule, and Duration tables. BMC AMI Utility Manager then generates a report (see Sample summary report) that lists the objects that would have been processed or skipped.

Important

REPORTALL tells BMC AMI Utility Manager to analyze the statement object against the criteria in the Exceptions, Criteria, and Schedule tables; REPORTONLYperforms the same action against the Exceptions and Criteria tables only.

Optionally, you can include a timestamp with the REPORTALL option. The timestamp must be in ISO 8601 format (YYYY-MM-DDTHH:MM:SS.SSSSSS). BMC AMI Utility Manager uses the timestamp when evaluating the START_TIME, END_TIME, MONTH, and DAY in the Schedule table. If you truncate a timestamp to the date, the time defaults to midnight (00:00:00:000000).

Example

This example generates an BMC AMI Utility Manager report but excludes the objects from processing. The product evaluates the Schedule table just before midnight on December 31, 2018:

//SYSIN DD *
  REORG OBJECTSET PROD.ACCOUNTING RTS(,REPORTALL(2018-12-31T23:59:59.999999))

Sample summary report

-- BMC Next Generation Technology   V vv.rr.mm

RTS REORG EXCLUDED TABLESPACE REPORT (STATEMENT 1)               
DATABASE  TABLESPACE             EXCLUDE                         
NAME      NAME        PART(S)    REASON                          
--------  ----------  ---------  --------------------------------
DSN8DCAT  ABC         0001       EMPTY_TABLESPACE       
DSN8DCAT  ABC         0002:0004  PASSED ALL RTS CRITERIA

RTS REORG EXCLUDED INDEX REPORT (STATEMENT 1)             
INDEX               INDEX                          EXCLUDE
CREATOR             NAME                PART(S)    REASON
------------------  ------------------  ---------  -----------------------
DSN8DCAT            ABC                 0002:0004  EXCLUDED BY SCHEDULE TABLE

GENERATESYSIN

Prevents the BMC AMI Utilities statement from being executed

BMC AMI Utility Manager expands the statement object (which can be a wildcard pattern) and runs it past the Exceptions and Selection criteria. Then BMC AMI Utility Manager reports just as with REPORTONLY but it also sends the list of selected objects to automation routine XRTSSYIN for custom processing.

Use this keyword if you are not using BMC AMI Utilities.

Examples

This example excludes an object from reorganization while generating Reorg statements that would have been processed during reorganization:

//SYSIN DD *
  REORG OBJECTSET PROD.ACCOUNTING RTS(,GENERATESYSIN)

The following example includes an application criterion:

REORG TABLESPACE MEDRECS.PATIENTS RTS(CRIT001,GENERATESYSIN)

Important

When you use the GENERATESYSIN keyword, all processing takes place in the master job. No server job is used.

GENERATESYSINALL

Like GENERATESYSIN, evaluates objects without processing them, like GENERATESYSIN but it also sends objects NOT selected for processing to XRTSSYIN wth "PASSED" added.

Then, XRTSSYIN can perform additional checks that are not available to BMC AMI Utility Manager.

For more information about XRTSSYIN, see Using-automation-control-points.

Examples
REORG TABLESPACE MEDRECS.PATIENTS RTS(,GENERATESYSINALL)
REORG TABLESPACE MEDRECS.PATIENTS RTS(CRIT001,GENERATESYSINALL)

Tells BMC AMI Utility Manager to report objects that are approaching their maximum size. BMC AMI Utility Manager sends the list of selected objects to XRTSSYIN automation control point for custom processing.

Example
REORG TABLESPACE MYDB.% RTS(MAXSIZE, 85, 85)

BMC AMI Utility Manager checks all table spaces and indexes in database MYDB for any that have surpassed 85% of the maximum allowed allocation.

Example
REORG TABLESPACE OBJECTSET PAYROLL RTS(MAXSIZE)

BMC AMI Utility Manager checks all table spaces and indexes defined to object set PAYROLL for any that have surpassed 90% (the default value) of the maximum allowed allocation.

Related topics

Automation-control-points

Using-BMC-AMI-Utility-Manager

Utility-Manager-syntax-diagram

 

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