Preparing for installation

The following topics describe the installation process and provide information that you can use to prepare your environment for the installation:

• • Upgrading from version 6.1 to 6.2
  • Installation worksheet
  • Downloading the installation files
  • Setting up the installation environment
  • Where to go from here

Upgrading from version 6.1 to 6.2

Perform a fresh installation to upgrade from version 6.1 of

BMC AMI Datastream for Ops

to version 6.2, to avoid complications and possible functionality issues.

If you must perform an SMP/E installation we recommend that before beginning the upgrade, you first copy parm members for SMP/E installations when updgrading from version 6.1 to version 6.2.

Installation worksheet

Use the following worksheet to help you collect the variable values that you need to specify when installing the product. If you do not know the values, contact your system administrator.

Variable Name	Description	Value
AMIHLQ	High-level qualifier for all the data sets to be allocated for your installation We recommend including the Datastream for Ops version number, such as CZA.AMI5901.
AMISC	SMS storage class for all the data sets allocated during the installation process
AMIMC	SMS management class for all the data sets allocated during the installation process This variable depends on your site requirements.
AMIVS	(For a non-SMS installation) This is the volume serial number

Downloading the installation files

You obtain the product installation files by downloading them from the BMC Electronic Product Distribution (EPD) website. Your ability to access product pages on the EPD website is determined by the license entitlements purchased by your company.

Download the installation package to your computer and unzip the contents. Verify that you have the following files:

• $$READAO.txt
• BXBvrmm.SPEyymm.trs
• EULA.pdf
• EULA.txt
• AO_Terse_Allocate.txt
• AO_Unterse.txt

The vrmm placeholder represents the version, release, and modification level. The yymm placeholder represents the year and month of small programming enhancement (SPE) releases. For example, SPE2201 refers to the SPE released in January 2022.

Setting up the installation environment

This section describes how to set up the installation environment.

Before you begin

Upgrade customers might need to perform one or both of the following tasks:

Create new base libraries

Create a new set of base libraries for a new version of

BMC AMI Datastream for Ops

. Do not reuse an existing set of libraries. 

The installation jobs delete and allocate all the necessary libraries to run the product.

Copy parm members for SMP/E installations when updgrading from version 6.1 to version 6.2

If you require an SMP/E installation, you can use the job STEPs TSO and COPYOLD to copy your 6.1 user parm members to the 6.2 installation. The parm members are copied even though this is a clean SMPE installation.

1. Modify the following job STEPs in the SMPEJCL SPEAPPLY job:
   • TSO—Change the LISTDS dataset so that it points to the 6.1 dataset that contains your parm members you want to copy. For example,
     LISTDS 'AMIHLQ.SCZA610.PARM' MEMBERS
   • COPYOLD—Change the INPARM DD statement so that it is the same as the 6.1 dataset specified in TSO.
2. Execute the SMPEJCL SPEAPPLY job during the normal SMP/E installation process.

Peparing the bootstrap jobs on the mainframe

This section describes how to set up the bootstrap, including allocated space for the data sets and untersing the installation file.

To allocate space for the bootstrap data sets

The tersed installation file is about 11 MB, which is larger than what most dynamic allocation allows for. To allocate space for the bootstrap data sets, modify and upload the terse allocation job file to the mainframe.

1. Upload the terse allocation text file to the mainframe using ASCII to EBCDIC conversion.
2. Open the terse allocation JCL file for editing.
3. Add your site-specific JOB card.
4. Change the following references to your variable value:
   
   • AMIHLQ
   • AMISC
   • (Optional) AMIMC (depends on site requirements)
5. Modify the file according to your SMS requirements:
   
   • If your site requires an SMS management class specification, uncomment the following JCL statements:
     • 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=
6. Run the customized job.

The job allocates space for the following data sets:

• AMIHLQ.CZAGENT.XMIT     
• AMIHLQ.CZAGENT.XMIT.TRS 

To upload and unterse the installation file

1. To unterse the installation file, upload the unterse job file to the mainframe using ASCII to EBCDIC conversion.

2. Using FTP, IND$FILE, or another transmit mechanism, upload the tersed file to the mainframe (AMIHLQ .CZAGENT.XMIT.TRS). 

   Important

   Ensure that you upload the tersed file as a binary file.

3. To unterse the bootstrap data set, open the unterse JCL file for editing.
4. Add your site-specific JOB card.
5. Change all references to AMIHLQ to your variable value.
6. Run the customized job.

The job unterses the bootstrap file into the previously allocated partitioned data set.

Where to go from here

Perform the procedures in the Installing-the-BMC-AMI-Datastream-for-Ops-product-files topic.