BMCUTIL table
This section describes the BMCUTIL table, which contains information about utilities that are currently running or started. The utilities use the table to control the use of utility IDs. Each BMC utility must have a unique ID for restart purposes. If you have more than one BMC utility installed, all of these utilities should share the same BMCUTIL table.
The utilities insert rows into the BMCUTIL table during the UTILINIT phase and update the table as the job status changes. The utilities delete rows from the BMCUTIL table during the UTILTERM phase.
BMCUTIL table
Column name | Data type | Description |
|---|---|---|
UTILID | CHAR(16) | Utility identifier |
STATUS | CHAR(1) | Execution status of the utility:
DASD MANAGER PLUS uses only X. |
UTILNAME | CHAR(8) | Name of the executing utility:
|
PHASE | CHAR(8) | Current phase of the utility BMC AMI Copy does not use this column. |
USERID | CHAR(8) | User ID executing the utility |
SSID | CHAR(4) | Db2 subsystem where the utility is running |
RESTART | CHAR(1) | Restart option:
DASD MANAGER PLUS does not use this column. Although UNLOAD PLUS accepts the RESTART, RESTART(PHASE), NEW/RESTART, and NEW/RESTART(PHASE) parameters, the utility executes as though you had specified the NEW parameter. |
NOTEID | CHAR(8) | TSO user ID to be notified DASD MANAGER PLUS does not use this column. |
DBNAME | CHAR(8) | (BMC AMI Reorg and REORG PLUS) name of the database containing the table or index space for which the last checkpoint was taken This value can be blank. The other utilities do not use this column. |
SPNAME | CHAR(8) | (BMC AMI Reorg and REORG PLUS) name of the table or index space for which the last checkpoint was taken This value can be blank. The other utilities do not use this column. |
SPSTATUS | CHAR(5) | (REORG PLUS only) space status before the utility stopped The other utilities do not use this column. |
COMMANDNO | SMALLINT | Not used (always 0) |
COMMAND | VARCHAR(256) | First 256 characters of the utility command text BMC AMI Reorg, DASD MANAGER PLUS, and BMC AMI Copy do not use this column. |
STATE | LONG VARCHAR | Utility state and sync information DASD MANAGER PLUS does not use this column. |
START_TIMESTAMP | TIMESTAMP | Starting timestamp of the utility |
Maintaining the BMCUTIL table
When a utility abends, rows might remain in the BMCUTIL table. If you need to control expansion of this table, use one of the following methods to delete rows:
- Use the TERM restart parameter on the EXEC statement to delete rows from the BMCUTIL and BMCSYNC tables. Do not delete any rows for instances of utilities that are awaiting restart.
Delete invalid rows in the BMCUTIL table. Do not delete any rows for instances of utilities that are awaiting restart.
DELETE
FROM creatorName.CMN_BMCSYNC
WHERE UTILID NOT IN
(SELECT UTILID FROM creatorName.CMN_BMCUTIL);