Common utility tables

This section describes the contents of the common utility, BMCHIST_STEP, and BMCHIST_OBJECT tables, considerations for these tables, and how to maintain them if necessary.

Overview of common utility tables

The BMC common utility tables contain information about the BMC utilities that you generate and submit through a BMC utility product.

Related topics

Managing-common-utility-tables

Key-concepts

The following table lists the tables that each product uses and each table’s default name and alias.

Important

CHECK PLUS, LOADPLUS, REORG PLUS, and UNLOAD PLUS use synonyms instead of aliases.


Table

Default name

Alias

Utilities that use this table

CMN_BMCDICT

BMC_BMCDICT

  • LOADPLUS
  • REORG PLUS

CMN_BMCHIST

BMC_BMCHIST

  • CHECK PLUS
  • BMC AMI Copy
  • LOADPLUS
  • BMC AMI Recover
  • REORG PLUS
  • UNLOAD PLUS

CMN_BMCSYNC

BMC_BMCSYNC

  • CHECK PLUS
  • BMC AMI Check
  • BMC AMI Copy
  • DASD MANAGER PLUS (BMCSTATS)
  • LOADPLUS
  • BMC AMI Load
  • BMC AMI Recover
  • BMC AMI Recovery Manager
  • REORG PLUS
  • BMC AMI Reorg
  • UNLOAD PLUS
  • BMC AMI Unload

CMN_BMCUTIL

BMC_BMCUTIL

  • CHECK PLUS
  • BMC AMI Check
  • BMC AMI Copy
  • DASD MANAGER PLUS (BMCSTATS)
  • LOADPLUS
  • BMC AMI Load
  • BMC AMI Recover
  • BMC AMI Recovery Manager
  • REORG PLUS
  • BMC AMI Reorg
  • UNLOAD PLUS
  • BMC AMI Unload

CMN_BMCXCOPY

BMC_BMCXCOPY

  • BMC AMI Copy
  • BMC AMI Log Master
  • BMC AMI Recover
  • BMC AMI Recovery Manager
  • REORG PLUS
  • UNLOAD PLUS
  • BMC AMI Unload



  • BMC AMI Load
  • BMC AMI Reorg
  • BMC AMI Unload
  • BMC AMI Check
  • BMC AMI Copy
  • BMC AMI Recover
  • BMC AMI Log Master
  • High-speed Apply Engine

Warnings and considerations for common utility tables

This topic describes important information that you need to know when using the common utility tables.

Warning

The following warnings apply to the common utility tables:

  • To prevent unpredictable results, do not run any of the following products against the BMC common utility tables or table spaces:
    • LOADPLUS
    • BMC AMI Load
    • REORG PLUS
    • BMC AMI Reorg
    • UNLOAD PLUS
    • BMC AMI Unload
  • Because BMC AMI Recover uses BMC tables during the recovery process, you cannot use BMC AMI Recover 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.
  • We strongly recommend 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 BMC AMI Copy as the copy utility, you must use SHRLEVEL CHANGE for the following spaces:
    • BMCUTIL
    • BMCHIST
    • BMCSYNC
    • BMCXCOPY
    • BMCHISTS
    • BMCHISTO

  • Supported versions of the following BMC products support the LOCKROW installation option:

    • CHECK PLUS
    • LOADPLUS
    • REORG PLUS
    • UNLOAD PLUS

    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:

    • BMC AMI Copy
    • DASD MANAGER PLUS
    • BMC AMI Recover

 

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