Installing and configuring the BMC AMI Defender component


The BMC AMI Defender for Ops Insight component is required to collect SMF records and pass them to the BMC AMI Ops Insight product for processing.

You can do a full install of BMC AMI Defender for Ops Insight, or you can install it as an update over a previous version.

To install BMC AMI Defender for Ops Insight

  1. From the BMC Electronic Product Download site (EPD) website, select 

    BMC AMI Ops Insight

     and download AMI Defender for Ops Insight 6.1.00 SPE2201.
    Your ability to access product pages on the EPD website is determined by the license entitlements purchased by your company.
    The downloaded file name is BMC-AMI-Defender-for-Ops-Insight-v6.1.00.SPE2201.4139-4140.zip.

  2. Unzip the downloaded package to a directory.
    The $$READOI.txt file contains a summary of these instructions.
  3. Copy the OI_Terse_Allocate.txt file to a JCL library on the mainframe, and customize the job according to the instructions in the file.
  4. Submit the job to preallocate the mainframe files required to install the product.
    The tersed file is close to 4 MB and might be larger than some systems can dynamically allocate using IND$FILE. The job allocates two data sets:
    • &PFX.CZAOPINS.XMIT.TRS holds the TRS file transferred from the PC to the mainframe in the following step
    • &PFX.CZAOPINS.XMIT holds additional information and JCL used to complete the installation
  5. Copy the OI_Unterse.txt file to a new member in the JCL library allocated in Step 4 (&PFX.CZAOPINS.XMIT).
  6. Copy or transfer the A0P6100.SPE2201.TRS file to the mainframe file allocated in Step 4 (&PFX.CZAOPINS.XMIT.TRS).
    You can use either the IND$FILE mainframe transfer tool or another tool, such as an FTP client.
  7. Customize the unterse file (OI_Unterse.txt) JCL member in &PFX.CZAOPINS.XMIT that you created in Step 5. Follow the customization instructions in the member and then submit the job.
    The job populates the other file allocated in Step 4 (&PFX.CZAOPINS.XMIT).
  8. Customize the INSTALL member of the &PFX.CZAOPINS.XMIT data set according to the instructions in the file, and submit it.
    After the job completes running, you have the following set of BMC AMI product libraries:
    • &PFX.CZAOPINS.ARCH9.LOAD
    • &PFX.CZAOPINS.BMCPSWD
    • &PFX.CZAOPINS.CNTL
    • &PFX.CZAOPINS.LOAD
    • &PFX.CZAOPINS.PARM
    • &PFX.CZAOPINS.XMIT
    • &PFX.CZAOPINSD.XMIT.TRS
  9. Modify the CZAPOI member of the PARM file as described in Updating-the-BMC-AMI-Defender-for-Ops-Insight-parameter-file.
    All procedures, JCL, and parameter files are contained in the PARM file, &PFX.CZAOPINS.PARM. Move the updated members to the corresponding location for the system on which BMC AMI Defender for Ops Insight will be run (PROCLIB, etc). Do not update the CNTL file, &PFX.CZAOPINS.CNTL, externally; it is used as part of maintenance updates to the BMC AMI Defender for Ops Insight.
  10. APF authorize &PFX.CZAOPINS.LOAD and &PFX.CZAOPINS.ARCH9.LOAD.
  11. Install a BMC key to your BMCPSWD data set.
  12. Proceed with To enable sysplex support.

Note

BMC AMI Defender includes a high-performance load library that requires IBM z/OS Version 2.3 or later. If you start the BMC AMI Defender 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.

To update BMC AMI Defender for Ops Insight

  1. From the BMC Electronic Product Download site (EPD) website, select 

    BMC AMI Ops Insight

     and download AMI Defender for Ops Insight 6.1.00 SPE2201.
    Your ability to access product pages on the EPD website is determined by the license entitlements purchased by your company.
    The downloaded file name is BMC-AMI-Defender-for-Ops-Ins-v6.1.00.SPE2201.4139-4140.zip.

  2. Unzip the downloaded package to a directory.
    The $$READOI.txt file contains a summary of these instructions.
  3. Copy the OI_Terse_Allocate.txt file to a JCL library on the mainframe, and customize the job according to the instructions in the file.
  4. Submit the job to preallocate the mainframe files required to install the product.
    The tersed file is close to 4 MB and might be larger than some systems can dynamically allocate using IND$FILE. The job allocates two data sets:
    • &PFX.SPEOPINS.XMIT.TRS holds the TRS file transferred from the PC to the mainframe in the following step
    • &PFX.SPEOPINS.XMIT holds additional information and JCL used to complete the installation
  5. Copy the OI_Unterse.txt file to a new member in the JCL library allocated in Step 4 (&PFX.SPEOPINS.XMIT).
  6. Copy or transfer the A0P6100.SPE2201.TRS file to the mainframe file allocated in Step 4 (&PFX.SPEOPINS.XMIT.TRS).
    You can use either the IND$FILE mainframe transfer tool or another tool, such as an FTP client.
  7. Customize the unterse file (OI_Unterse.txt) JCL member in &PFX.SPEOPINS.XMIT that you created in Step 5. Follow the customization instructions in the member and then submit the job.
    The job populates the other file allocated in Step 4 (&PFX.SPEOPINS.XMIT).
  8. Customize the UPDATE member of the &PFX.SPEOPINS.XMIT data set according to the instructions in the file, and submit it.
    After the job completes running, you have the following set of BMC AMI product libraries:

    Backed up data sets before update applied

    • &PFX.BKPOPINS.ARCH9.LOAD
    • &PFX.BKPOPINS.CNTL
    • &PFX.BKPOPINS.LOAD
    • &PFX.BKPOPINS.PARM

    Newly updated data sets with SPE applied

    • &PFX.CZAOPINS.ARCH9.LOAD
    • &PFX.CZAOPINS.BMCPSWD
    • &PFX.CZAOPINS.CNTL
    • &PFX.CZAOPINS.LOAD
    • &PFX.CZAOPINS.PARM

    SPE install data sets

    • &PFX.SPEOPINS.XMIT
    • &PFX.SPEOPINSD.XMIT.TRS
  9. Modify the CZAPOI member of the PARM file as described in Updating-the-BMC-AMI-Defender-for-Ops-Insight-parameter-file.
    All procedures, JCL, and parameter files are contained in the PARM file, &PFX.CZAOPINS.PARM. Move the updated members to the corresponding location for the system on which BMC AMI Defender for Ops Insight will be run (PROCLIB, etc). Do not update the CNTL file, &PFX.CZAOPINS.CNTL, externally; it is used as part of maintenance updates to the BMC AMI Defender for Ops Insight.

    Best practice
    Reference your previously tailored CZAPOI member in the backup data set &PFX.BKPOPINS.PARM and reconcile with the new CZAPOI member in &PFX.CZAOPINS.PARM.

  10. Proceed with To enable sysplex support.

To enable Sysplex support

Pereform the following procedure to enable capturing of the sysplex name from BMC AMI Defender data:

  1. Locate the CZDOI member in the PARM data set as specified in the Defender PROC for CZAPARMS.
  2. Locate the following lines in the CZDOI member:

    DEF OI_DB2Plex '' Universal() FChar(8 SUB   ) GPreamble(X'80' 8)
    DEF OI_RMFPlex '' Universal() FChar(8 SUB   ) GPreamble(X'80' 8)

  3. On the two lines, insert TB as follows:

    DEF OI_DB2Plex '' Universal() FChar(8 SUB TB) GPreamble(X'80' 8)
    DEF OI_RMFPlex '' Universal() FChar(8 SUB TB) GPreamble(X'80' 8
  4. Save the edited CZDOI member and recycle all BMC AMI Defender address spaces.


Where to go from here

After you install the BMC AMI Defender component, install BMC AMI Ops Insight.

 

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