Common utility tables
The following topics describe the contents of the common utility tables, considerations for these tables, and how to maintain them if necessary:
The BMC common utility tables contain information about the BMC utilities that you generate and submit through a BMC utility product.
The following table lists the tables that each utility uses and each table’s default name and synonym.
Common utility tables
Utilities that use this table
Warnings and considerations for common utility tables
This section describes important information that you need to know when using the common utility tables.
The following warnings apply to the common utility tables:
Do not run LOADPLUS, REORG PLUS, or UNLOAD PLUS against the BMC common utility tables or table spaces. Doing so can cause unpredictable results.
Because RECOVER PLUS uses BMC tables during the recovery process, you cannot use RECOVER PLUS to recover any BMC table except the BMCHIST table.
Do not run the RUNSTATS utility against the BMC common utility tables. Doing so can negatively impact utility performance.
BMC strongly recommends that you use the ISOLATION (UR) bind option and issue SQL COMMIT statements when querying the tables in the BMC database. If objects in the BMC database are restricted for UPDATE, the executing BMC utilities might not be able to complete successfully.
Note the following considerations:
Some columns in the tables are present for compatibility with specific BMC utilities and are not used by all of the utilities.
If you have applications that depend on the structure or content of these tables, be aware that these tables are subject to change.
In general, the utility tables should not require maintenance, with the exception of BMCHIST.
You should back up the BMC table spaces on a regular basis to enable recoveries. If you use COPY PLUS as the copy utility, you must use SHRLEVEL CHANGE for the following spaces:
Supported versions of the following BMC products support the LOCKROW installation option:
If the value of the option is YES (which is the default value), the products use MVS enqueues instead of SQL LOCK TABLE statements to serialize updates to the BMCSYNC and BMCUTIL tables.
The following BMC products always use MVS enqueues for serialization when updating the BMCSYNC and BMCUTIL tables:
DASD MANAGER PLUS