Installing and configuring BMC AMI Datastream for Ops

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 base version and configure the selection parameters. When a new version is released, you can update the product libraries.

This topic contains the following sections:

• • To install the base version
  • To configure the selection parameters
  • To update the product libraries

To install the base version

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.1.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.CZAMIOPS.XMIT.TRS will contain the TRS file that you will transfer from the PC to the mainframe in step 5.
   • &PFX.CZAMIOPS.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.CZAMIOPS.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.CZAMIOPS.XMIT).
8. Customize the INSTALL member of the &PFX.CZAMIOPS.XMIT data set according to the instructions in the member and submit it.
   After the job completes running, you have the following set of product libraries:
   • &PFX.CZAMIOPS.ARCH9.LOAD
   • &PFX.CZAMIOPS.BMCPSWD
   • &PFX.CZAMIOPS.CNTL
   • &PFX.CZAMIOPS.LOAD
   • &PFX.CZAMIOPS.PARM
   • &PFX.CZAMIOPS.XMIT
   • &PFX.CZAMIOPS.XMIT.TRS
9. Modify the CZAPAO member of the &PFX.CZAMIOPS.PARM data set as described in To configure the selection parameters.
10. 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.
11. Use APF to authorize &PFX.CZAMIOPS.LOAD and &PFX.CZAMIOPS.ARCH9.LOAD.
12. Specify a key for your BMCPSWD data set. 

To configure the selection parameters

After you install BMC AMI Datastream for Ops and update the product libraries, you must configure the selection parameters to enable the application to send BMC AMI Ops performance data to your SIEM.

1. Open the member specified in the PARMS parameter of the BMC AMI Datastream for Ops started task procedure. For example, the sample CZAMIOPS JCL in the PDS &PFX.CZAMIOPS.CNTL uses PARMS=CZAPAO.
   
   CZAPAO is contained in the PDS identified by the CZAPARMS ddname. For example,
   //CZAPARMS DD  DSN=amihlq.CZAMIOPS.PARM,DISP=SHR

   Important

   CZAPAO contains the customized parameters for connecting the BMC AMI Datastream for Ops task to the BMC AMI Ops task. Use CZAPAO as a sample to create multiple members if you require more than one set of options. Make sure that you retain copies of these members.

   CZAPAO is overwritten when you upgrade BMC AMI Datastream for Ops to a new SPE.

   For an example of the CZAPAO member, see Customizing-for-a-BMC-AMI-Ops-extension.

2. Modify the OPTIONS INSTNAME statement to specify the relevant instance of BMC AMI Datastream for Ops.
   INSTNAME identifies and isolates the relevant instance of BMC AMI Datastream for Ops running on your system (LPAR).

   • You can run multiple instances on multiple LPARs.
   • If you run multiple instances on the same LPAR, each instance must have a unique INSTNAME.
   • If you run multiple instances each on a separate LPAR, they do not require a unique INSTNAME.

   A BMC AMI Datastream for Ops INSTNAME must have the following characteristics:

   • From one to sixteen characters long
   • First character can be numeric
   • Can begin and end in quotation marks

   • Can contain blank spaces or parentheses

     
     

3. Modify the SERVER statement to include the following information:

   • IP address or DNS entry for the z/OS TCP/IP server on which BMC AMI Ops is running
   • Port number required for the server. The port number must be between 1024 and 65535. The default is 32000.
   • The parameters TRANS(TCP) and MAXMSG(32768)

   Use the following syntax for the SERVER statement:
   SERVER ipAddress|dnsName:portNumber TRANS(TCP) MAXMSG(32768)

   Example

   SERVER SJSD:42000 TRANS(TCP) MAXMSG(32768)

To update the product libraries

Use the following procedure to install the product library update for BMC AMI Datastream for Ops:

1. From the EPD website, download the latest zip file for the BMC AMI Datastream for Ops product.

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 PS data set or a 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 and the JCL 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. Customize the UPDATE member of the &PFX.SPEOPS.XMIT data set according to the instructions in the member and submit it.
   After the job completes running, you have the following sets of product libraries, depending on the scenario:

   Scenario	Product libraries
   Backed up data sets before update applied	&PFX.BKPOPS.ARCH9.LOAD &PFX.BKPOPS.CNTL &PFX.BKPOPS.LOAD &PFX.BKPOPS.PARM
   Newly updated data sets with SPE applied	&PFX.CZAMIOPS.ARCH9.LOAD &PFX.CZAMIOPS.BMCPSWD &PFX.CZAMIOPS.CNTL &PFX.CZAMIOPS.LOAD &PFX.CZAMIOPS.PARM
   SPE install data sets	&PFX.SPEOPS.XMIT &PFX.SPEOPS.XMIT.TRS

9. Modify the CZAPAO member of the &PFX.CZAMIOPS.PARM data set as described in To configure the selection parameters.

   Best practice
   Reconcile the CZAPAO member already in the backup data set &PFX.BKPOPS.PARM with the new CZAPAO member in &PFX.CZAMIOPS.PARM.

10. 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.