Component configuration

BMC AMI Command Center uses the following components:

• Common Interface Server (CIS)
  For more information, see Overview of Common Interface Server.
• BMC Execution Component for z/OS
  For more information, see Overview of BMC Execution Component for z/OS.

These components then interface with subsystems and programs running on the mainframe.

The following diagram shows the relationship between BMC AMI Command Center and the components:

Overview

You access BMC AMI Command Center for Db2 using a browser. The browser downloads the client to its local cache. Once downloaded, the browser sends your login request to the CIS, which provides security verification.

After verification, the browser sends and receives your requests to and from the CIS. The CIS routes the request to the BMC AMI Command Center server component. The BMC AMI Command Center server component sends a request to one of the following interface services provided by the CIS:

• BMC Execution for z/OS (DBC) – Provides an access point for communicating with DBC agents that communicate with other programs and systems, such as:
  • Db2 subsystems
  • BMC AMI Catalog Manager for Db2
  • BMC AMI Change Manager for Db2
  • BMC AMI Apptune for Db2
  • BMC AMI SQL Explorer for Db2
  • BMC AMI Recover for Db2
  • DBC agents on other LPARs
• MF JES - Provides the services needed to access job information on the mainframe LPAR on which CIS is running.
• MF data set – Provides the services needed for accessing data sets and members on the mainframe LPAR on which CIS is running.

Configuration requirements

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

Common Interface Server (CIS)

The following requirements apply if you have multiple BMC AMI Command Center installations sharing a single BMC AMI Command Center repository:

• Each CIS has its own BMCHFS directory that identifies the location (Db2 subsystem) of the BMC AMI Command Center repository. If multiple BMC AMI Command Center installations share a repository, all the CIS BMCHFS directories must point to the same location.
• All BMC AMI Command Center installations must have the same maintenance level (that is, the same PTFs from CIS 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 the 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.