Preparing for update

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

• • Update worksheet
  • Downloading the update files
  • Setting up the update environment
  • Upgrading from version 6.2 to 7.1
  • Where to go from here

Update worksheet

Use the following worksheet to help you collect any variables that you need to specify when updating 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 update We recommend including the BMC AMI Datastream version number, such as CZA.AMI7100.
AMISC	SMS storage class for all the data sets allocated during the update process
AMIMC	SMS management class for all the data sets allocated during the update process This variable depends on your site requirements.
AMIVS	(For a non-SMS update) Volume serial number

Downloading the update files

Whether you are installing an SPE or a PTF, you obtain the product update 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.

You can also navigate to the files on the EPD website as follows:

1. Go to Product Downloads in BMC Support Central.

2. If the Export Compliance And Access Terms page is displayed, enter the relevant data and click Continue.

   Warning

   Important
   You must enable pop-ups for this web page in your browser.

3. Locate the product name by browsing or searching in the Search for Product field. If you have marked the product as a favorite, click Favorites.
4. Under the product name, click the required supported version.
5. To install a PTF, click the Patches tab.
6. Select the required file and click Download.
7. To view the list of PTFs, locate the required product name and version, and click the PTF text file.
8. Download the update 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,  BXB7100.SPE2504.trs is BMC AMI Datastream version 7.1.00, released in April 2025.

When installing PTF patches, the following file name convention is used:
BMC-AMI-Datastream-vrmm.SPEyymm.buildNumber.zip

For example, BMC-AMI-Datastream-v7.1.03.SPE2507.1990.01.zip.

Setting up the update environment

This section describes how to set up the update environment.

Before you begin

You might need to perform one or more of the following tasks:

Back up product files

The update process automatically creates a backup of exiting product files before applying the update.

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.

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 upgrading from version 6.2 to version 7.1.

Preparing 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 update file.

To allocate space for the bootstrap data sets

The tersed update 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_Allocate.txt job to the mainframe.

1. Upload the Terse_Allocate.txt text file to the mainframe using ASCII to EBCDIC conversion.
2. Open the Terse_Allocate.txt 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 update process allocates the following data sets:

• AMIHLQ.SPEAGENT.XMIT
• AMIHLQ.SPEAGENT.XMIT.TRS

To upload and unterse the update file

1. Using FTP, IND$FILE, or another transmit mechanism, upload the ADZvrmm.trs file to the mainframe ( AMIHLQ.SPEAGENT.XMIT.TRS). 

   Warning

   Important

   Ensure that you update ADZvrmm.trs as a binary file.

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

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

Upgrading from version 6.2 to 7.1

Perform a fresh installation to upgrade from version 6.2 of BMC AMI Datastream for Ops to version 7.1, to avoid complications and possible functionality issues. For information about installing the product, see Preparing-for-installation.

Copy parm members for SMP/E installations when upgrading from version 6.2 to version 7.1

If you require an SMP/E installation, you can use the job STEPs TSO and COPYOLD to copy your 6.2 user parm members to the 7.1 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.2 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.2 dataset specified in TSO.
2. Execute the SMPEJCL SPEAPPLY job during the normal SMP/E installation process.

Where to go from here

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