Updating the BMC AMI Datastream for Ops product files

In the &PFX.SPEOPS.XMIT data set there is an UPDATE member that you customize and run to update the product files.

Before you begin
To update the BMC AMI Datastream for Ops product files
Determine the applicable load library to use
To restore the backup files created by the update job
Comparing new features and customized $$$nnnnn members
Where to go from here

For information about installing BMC AMI Datastream for Ops, see Installing.

Before you begin

Perform the procedures in Preparing-for-update.

Important

UPDATE automatically creates a backup of the existing product files before beginning the actual update. The files are allocated as AMIHLQ.BKPAGENT.xx.
You cannot rerun UPDATE without first running RESTORE.
UPDATE does not allocate new data sets. It only updates the existing product data sets by replacing members in the product libraries.

To update the BMC AMI Datastream for Ops product files

Open the UPDATE member for editing.
Add your site-specific JOB card.
Change the following references to your variable value:
- AMIHLQ
- AMISC
- (Optional) AMIMC (depends on site requirements)
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=

Run the customized job.
The job allocates and populates the following data sets, depending on the scenario:

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

Modify the CZAPAO member of the AMIHLQ.PARM data set as described in To configure the selection parameters.
SuccessBest practice
Reconcile the CZAPAO member already in the backup data set AMIHLQ.BKPOPS.PARM with the new CZAPAO member in AMIHLQ.PARM.
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 AMIHLQ.SAMP data set externally; it is used for maintenance updates to BMC AMI Datastream for Ops.

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.LOAD	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.ARCH9.LOAD	Architecture level 9 load library You can use this library if you are not running on the latest IBM hardware and operating system. It is compiled and linked at architecture level 9, so this load library can run on IBM zEnterprise 114 or 196 hardware, or better.

To restore the backup files created by the update job

Open the RESTORE member for editing.
Add your site-specific JOB card.
Change the following references to your variable value:
- AMIHLQ
- AMISC
- (Optional) AMIMC (depends on site requirements)
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=
Run the customized job.

The restore job deletes and reallocates the product files and then restores them from the backup files. If your site uses volume-specific authorization statements, you may need to review your APF authorizations for the product load libraries.

Comparing new features and customized $$$nnnnn members

The customizable $$$nnnnn members in the hlq.PARM data set represent equivalent CZAnnnn members. Your existing $$$nnnnn members are not modified during upgrade and are usually upward compatible. Any new functionality added to CZAnnnn members have default values that do not negatively impact earlier versions of $$$nnnnn members.

Important

Although we will strive to maintain upward compatibility with JCL and PARMs, we cannot guarantee it. For example, the AMISSID parameter (introduced in version 6.0.02) on the CZAMIOPS JCL requires that you modify it should there be more than one agent address space on an LPAR. Prior JCL (version 5.9.02 and earlier) did not include this execution parameter and consequently took the default for every agent address space.

BMC documents changes in CZAnnnn members in release notes and SPE technical bulletins, so that you can include features in your $$$nnnnn members. Changes that do not affect $$$nnnnn members are annotated in case you modified something else in your PARM file.

SPEs include all previous SPE enhancements and patches. We recommend that you review all notices since your last installation to make sure that you are aware on any configuration changes. For the full list of patches and SPEs, see Notices.

After you update the product, compare the following customizable members in the hlq.PARM data set for any new required customizations:

Custom member	Description	Reference
$$$CONFG	Event and SMF record family selection	Customizing-for-a-proprietary-syslog-extension
$$$SELCT	Event and SMF record selection	Customizing-required-events-with-SELECT
$$$SERVR	Processing options and SIEM server identification	Customizing-for-a-proprietary-syslog-extension

We strive to minimize the impact to the supplied sample JCL. As we add new execution parameters and data sets, we try to make changes that allow upward compatibility with existing JCL. We do this through the use of default values that should not have a negative impact on earlier product releases.

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.