Limited supportBMC 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 Ops Monitor for Db2 13.1 image-2024-5-19_8-5-1.png .

Defining the connection to the BMC AMI Ops Monitor for Db2 - Data Collector

Use the following procedure to activate the functions that are provided by the 

BMC AMI Ops Monitor for Db2

 - Data Collector component.

You can define the Data Collector connection during BMC AMI Ops configuration, or you can do it manually as described in the following procedure.

To define the connection to the BMC AMI OpsM for Db2 - Data Collector

If you did not run configuration, activate the interface from the BBI-SS PAS to the Data Collector as follows:

  1. Concatenate the Data collector BMCLINK library (if it is different than the BMC AMI OpsM for Db2 BMCLINK) in the BMC AMI OpsM for Db2 BBI-SS PAS JCL to the STEPLIB DD.  If during installation you chose to customize the runtime LLQs, use the following list of SMP/E Target load library names to concatenate the required runtime libraries.

    • BBLINK
    • DOMLINK
    • PSSLINK
    • DBCLINK
    • USCLINK

    For more information, see the Installation System documentation.

    Note

    If you are installing the OPERTUNE for DB2 product you should include the OPERTUNE load library, DDTLINK (if BMCLINK was not created). Including the load library to activate the API will also activate the BMC AMI OpsM for Db2 interface to OPERTUNE that allows you to change ZPARMs from views. Before any change is allowed, security is checked in both products.

    This step activates the connection logic and allows trace data that was collected in the Data Collector to be retrieved and displayed in BMC AMI OpsM for Db2 views.

    You need to indicate the Data Collector to which BBI-SS PAS should connect. You can direct the PAS to connect to a specific Data Collector by specifying the parameter CDC in the BBPARM member DMRBEXxx for each Db2 target.

  2. Start the Data Collector started task by using the customized procedure DBC$STC. Copy DBC$STC from the UBMCSAMP library to the system PROCLIB dataset and (optionally) rename the started task. 

  3. To enable hyperlinks from BMC AMI OpsM for Db2 views to related reports in the other Db2 Performance products and some additional BMC AMI OpsM for Db2 - Data Collector reports, manually move the customized CLIST DOMC from hilevel.BBSAMP to hilevel.SBBCLIB and ensure that hilevel.SBBCLIB is allocated in the BMC AMI Ops CLIST by the BBCLIB DD statement after hilevel.BBCLIB.

  4. Ensure that the password that you included in the BMC AMI Ops BMCPSWD data set (BDSTBL3x for BMC AMI OpsM for Db2, SPDTBL3x for the BMC System Performance for Db2solution, or MV2TBL3x for the BMC AMI Ops for Db2 solution) is also included in the Data Collector HLQ.BMCPSWD data set.

    Note

    If you need to make changes to the Administration dialog when the Data Collector is running and the BMC AMI OpsM for Db2 – Data Collector component is not yet configured, you can use the LGCISPF member of the UBMCCLIB data set to invoke a Report Manager session and access the online Administration panels.

    Related topic

    Customizing-after-installation

    BBPARM-data-set-members

 

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