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 Datastream for Ops 7.1.

Installing the BMC AMI Datastream for Ops product files

BMC AMI Datastream for Ops collects BMC AMI Ops performance records and passes them to your SIEM, such as Splunk, for analysis and reporting. To use BMC AMI Datastream for Ops, you must install the product files and configure the selection parameters.

For information about upgrading BMC AMI Datastream for Ops, see Updating.

Before you begin

Perform the procedures in the Preparing-for-installation topic.

To install the BMC AMI Datastream for Ops product files

Use the following procedure to install the base version of BMC AMI Datastream for Ops:

  1. From the BMC Electronic Product Download (EPD) website, download the zip file for the BMC AMI Datastream for Ops 6.2.00 product.
    Your ability to access product pages on the EPD website is determined by the license entitlements purchased by your company.

  2. Unzip the downloaded package to a directory.
    The $$READAO.txt file contains a summary of these instructions.
  3. Copy the AO_Terse_Allocate.txt file to a physical sequential (PS) data set or a partitioned data set (PDS) member on the mainframe and customize the job according to the instructions in the file.

  4. Submit the job to preallocate the mainframe data sets required to install the product.

    Important

    The tersed file might be larger than some systems can dynamically allocate using IND$FILE.

    The job allocates two data sets:

    • &PFX.SPEOPS.XMIT.TRS will contain the TRS file that you will transfer from the PC to the mainframe in step 5.
    • &PFX.SPEOPS.XMIT contains additional information, including the JCL library that is used to complete the installation.
  5. Copy or transfer the BXBvrmm.SPEyymm.TRS file to the mainframe data set allocated in step 4 (&PFX.SPEOPS.XMIT.TRS).
    You can use either the IND$FILE mainframe transfer tool or another tool, such as an FTP client.
  6. Copy the AO_Unterse.txt file to a PS data set or a PDS member on the mainframe.
  7. Customize the unterse JCL job that you created in step 6. Follow the customization instructions in the job and then submit the job.
    The job populates the other data set allocated in step 4 (&PFX.SPEOPS.XMIT).
  8. Open the INSTALL member for editing.
  9. Add your site-specific JOB card.
  10. Change the following references to your variable value:
    • AMIHLQ
    • AMISC
    • (Optional) AMIMC (depends on site requirements)
  11. Modify the file according to your SMS requirements:
    • If your site requires an SMS management class specification, uncomment the following JCL statements:
      •  All MGMTCLAS=&MCLASS.
      • SET MCLASS=
    • If you do not use SMS, modify the file as follows:
      • Change all references to AMIVS to your variable value.
      • Comment out the following JCL statements:
        • All STORCLAS=&SCLASS.
        • All MGMTCLAS=&MCLASS.
        • SET SCLASS=
        • SET MCLASS=
      • Uncomment the following JCL statements:
        • All VOL=SER=&VOLSER.
        • SET VOLSER=
  12. Run the customized job.The job allocates and populates the following data sets:
    • &PFX.CZAMIOPS.ARCH9.LOAD
    • &PFX.CZAMIOPS.BMCPSWD
    • &PFX.CZAMIOPS.CNTL
    • &PFX.CZAMIOPS.LOAD
    • &PFX.CZAMIOPS.PARM
    • &PFX.CZAMIOPS.XMIT
    • &PFX.CZAMIOPS.XMIT.TRS
  13. Modify the CZAPAO member of the &PFX.CZAMIOPS.PARM data set as described in To configure the selection parameters.
  14. Move the updated members to the corresponding location on the system on which BMC AMI Datastream for Ops runs (for example, PROCLIB). 
    Do not update the &PFX.CZAMIOPS.CNTL data set externally; it is used for maintenance updates to BMC AMI Datastream for Ops.
  15. Use APF to authorize &PFX.CZAMIOPS.LOAD and &PFX.CZAMIOPS.ARCH9.LOAD.
  16. Specify a key for your BMCPSWD data set. 

Important

BMC AMI Datastream for Ops includes a high-performance load library (&PFX.CZAMIOPS.LOAD) that requires IBM z/OS Version 2.3 or later. If you start the BMC AMI Datastream for Ops agent on an earlier version of z/OS, a U4038-1 abend occurs. The abend occurs before the agent starts because the language environment (LE) cannot initialize its services. If a U4038-1 abend occurs, start the agent with LOAD=ARCH9.LOAD.

Determine the applicable load library to use

Use the applicable load library with BMC AMI Datastream for Ops. The data sets must be authorized program facility (APF) authorized.

If you do not know which library to use, contact your system administrator.

Load library

Description

AMIHLQ.CZAGENT.LOAD

This is the default load library.

This version of the code is tuned for the best performance on the most current, generally-available IBM hardware and operating system.

AMIHLQ.CZAGENT.ARCH9.LOAD

If you are not running on the latest IBM hardware and operating system, you can use this library. It is compiled and linked at architecture level 9 so this load library can run on IBM zEnterprise 114 or 196 hardware or better.

Where to go from here

To enable BMC AMI Datastream for Ops to send BMC AMI Ops performance data to your SIEM, see Configuring-the-SIEM-selection-parameters.

Related topics

Installing

Sample-CZAMIOPS-JCL-for-running-BMC-AMI-Datastream-for-Ops-as-a-started-task

 

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