Integrating with BMC AMI zAdviser


Related topics

Integrating

Defining-aliases-to-access-the-product-tables

Creating-the-extract-JCL-used-to-transmit-data-to-zAdviser

BMC AMI zAdviser is an application performance management (APM) tool designed specifically for mainframe environments. It provides performance monitoring, analysis, and reporting for IBM z/OS systems, allowing organizations to optimize the performance of their critical mainframe applications.

Before you begin

You must have the BMC AMI zAdviser product set up in your environment. For more information, see BMC AMI zAdviser documentation.

To integrate your product with BMC AMI zAdviser

You can perform the following tasks to integrate your product with BMC AMI zAdviser:

  1. Define aliases to access the product table
  2. Prepare the time stamp file
  3. Create JCL to extract data from your product
  4. Transmit data from your product to BMC AMI zAdviser

Task 1: Define aliases to access the product tables

Define aliases in your Db2 subsystem so that the extract process can read the product tables. For more information, see Defining-aliases-to-access-the-product-tables.

Task 2: Prepare the time stamp file

The JCL that extracts data from the product tables for transmission to BMC AMI zAdviser references a time stamp file to control how much data you send. The product includes an example:

rtehlq.BMCCLIB(AINZprd)

Replace prd with one of the following three character product codes:

  • ACM—BMC AMI Change Manager
  • UTL—BMC utilities (BMC AMI Utilities, PLUS Utilities, BMC AMI Copy for Db2, and BMC AMI Recover for Db2)

The time stamp member includes a default date and time of January 1, 2021, 00:00. The extract process extracts all data collected since that date. When the extract JCL runs, the extract process updates the time stamp member with the date and time of the latest record extracted for transmission to BMC AMI zAdviser. The next run of the extract process starts with the updated date and time.

Important

As the timestamp file sets the default date as January 1, 2021, 00:00, the first run of the extract JCL is expected to extract more data than usual, and the send JCL takes a long time to complete. To avoid this, you can modify the default date to a more current date, reducing the amount of data processed.

We recommend that you make a copy of the AINZprd member and place it in a data set that the extract process can update.

Task 3: Create the extract JCL

The product includes sample JCL in rtehlq.BMCCLIB(AINZEXTR) that you can use to run the extract process. Before you can run the JCL, you must modify it for your environment. For more information, see Creating-the-extract-JCL-used-to-transmit-data-to-zAdviser.

Task 4: Transmit data to BMC zAdviser

We recommend regularly running the modified extract JCL to transmit your data to BMC AMI zAdviser. The extract process writes data to SMF in a format that BMC AMI zAdviser can read. For more information, see BMC AMI zAdviser documentation.

 

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