Skip to Content

 

Information
Limited support BMC 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 Command Center for Db2 13.2

Component configuration

The following configuration requirements apply to the components that work with BMC AMI Command Center.

Related topic

Planning

User Interface Middleware (UIM)

  • You must have READ/WRITE privileges for the UIM BMCHFS data set.
  • The following requirements apply if you have multiple BMC AMI Command Center installations sharing a single BMC AMI Command Center repository:
    • There must be only one UIM BMCHFS data set per BMC AMI Command Center repository. If multiple BMC AMI Command Center installations share a repository, they must also share the associated UIM BMCHFS data set.
    • All BMC AMI Command Center installations must have the same maintenance level (that is, the same PTFs from UIM STEPLIB and DBC GUD agent LOADLIBs).

BMC Execution Component for z/OS (DBC)

BMC AMI Command Center uses GUD agents that require the Db2 DSNLOAD library. Unless you have already included that library in your LINKLIST, you must add the Db2 DSNLOAD library to one of the following locations:

  • For DBC version 10.1, add the Db2 DSNLOAD library to the <LOADLIB> tags in the GUDINIT step of the $480INIT job.
  • For DBC version 11.1, add the Db2 DSNLOAD library to the GUD1210 member of the hlq.DBCENV dataset by including a row like LOADLIB=hlq.DSNLOAD.

For more information, see Knowledge article 000159016 on BMC Support Central website (http://www.bmc.com/support).

The DBC address space must have WRITE privileges to SYSPRINT

The DBC$STC started task procedure runs under the authority of the user defined in the DBC$STC procedure. However, individual applications (such as BMC AMI Command Center) or agents that run in the DBC address space run under the authority of the application user requesting services from the application. These applications or agents attempt to write to SYSPRINT, typically for diagnostic purposes in abnormal conditions or when BMC Support provides instructions to activate debugging for troubleshooting purposes.

When these conditions occur, the application is running under the authority of the application user and not the DBC$STC user. Therefore, the application user must have WRITE privileges to SYSPRINT.

You should define SAF RULES to allow all BMC AMI Command Center users to write to SYSPRINT.

 

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

BMC AMI Command Center for Db2 12.1