Upgrading the agent

Before you begin

Verify that the agent’s installation prerequisites are met. For more information, see BMC-AMI-Cloud-agent-requirements.

Verify that the z/OS Java is version 8 64-bit SR6 FP25 or later. Using an earlier Java version would result in an agent startup failure with message number ZM91005E.

Verify the Java version and change the Java installation directory by using the following commands:

Task 1: To obtain the installation files

Skip this task if you have already downloaded the installation files and obtained a license key as explained in Upgrading-the-management-server-on-Linux or Upgrading-the-management-server-on-zCX.

1. Go toElectronic Product Distribution (EPD) and log in.

2. Using the search bar, search for either BMC AMI Cloud Data or BMC AMI Cloud Vault. Both product files are composed with the same binaries.
3. Click on version that you want to download. 
4. On the Product tab, select the files and click Download.

Task 2: To upload the agent TAR file to the installation directory

Use FTP or a similar utility to upload the BMC AMI Cloud product's installation tar file to the BMC AMI Cloud product's installation directory. Use Passive Mode if it is supported by the FTP client. The tar file must be uploaded in binary mode.

Task 3: To upgrade the agent binaries

In OMVS, extract the tar file and replace the agent symbolic link with a reference to the new directory, as shown in the following example:

Task 4: To copy the BMC AMI Cloud libraries from USS to PDS and modify

Edit and submit the JCL CPY#PDS located in /usr/lpp/model9/agent/installation to create the BMC AMI Cloud LOADLIB, SAMPLIB, and EXEC PDS files.

After the successful completion of CPY#PDS, update the following SAMPLIB PDS members:

Modify M9AGENT:

Optional parameters for M9AGENT:

Use the CONF_HOME parameter to activate more than one agent in the same LPAR. This parameter allows the agents to use the same BMC AMI Cloud installation files and libraries, but each will have a different configuration directory. The recommendation is to have one agent per LPAR, while all agents in the same GRS complex point to the same BMC AMI Cloud complex. However, additional agents in the same LPAR might be required if the following conditions exist:

• You are using a subplex.
• You are running both development and production environments.
• You are pointing different agents to different cloud storage.

The CONF_HOME parameter must precede the stdenv-main.sh statement. The following is an example of using the parameter:

Modify M9SAPI:

Modify M9LIFECY:

Copy M9AGENT, M9SAPI, M9LIFECY to your local libraries and reapply site modifications.

Task 5: To upgrade the BMC AMI Cloud Command Line Interface

Customize the M9CLI REXX in the EXEC PDS to match installation standards:

Copy the M9CLI EXEC to a site standard local EXEC library concatenated in the logon procedure.

Task 6: To upgrade automatic recall

1. Use the M9UNHOOK from the currently running version to uninstall the previous intercept. The expected RC is 0:

   S M9UNHOOK

   If another intercept was installed on top of the BMC AMI Cloud intercept, the uninstall process finishes with RC=4. In this case, the BMC AMI Cloud intercept is not removed but rather logically disabled, to prevent harming the subsequent intercept. This is a valid situation that will be corrected by the next IPL. You can also remove the top intercept and then remove the BMC AMI Cloud intercept again.

2. Replace the previously installed release and update the PROGxx configuration as follows:
   1. Copy the new M9HOOK and M9UNHOOK from the SAMPLIB to your local library and reapply site modifications.

   2. Add the following statements, replacing <VOLSER> with the relevant volume name:

      APF ADD DSNAME(SYS2.MODEL9.V411.LOADLIB) VOLUME(<VOLSER>)
      LPA ADD DSNAME(SYS2.MODEL9.V411.LOADLIB) MOD(ZM9CPTN)
      LPA ADD DSNAME(SYS2.MODEL9.V411.LOADLIB) MOD(ZM9S26X)
   3. Use the SET PROG=XX operator command to apply the changes.
   4. Verify that the command has ended successfully.
   5. Load the intercept and exit modules to the Dynamic LPA. Do not use MLPA or PLPA to load the modules.

3. Activate the automatic recall function by using the following command. The expected RC is 0:

   S M9HOOK

4. If you are using another data management product together with BMC AMI Cloud Data, add the following DD statement to the other product procedure to avoid collisions:

   //ZM9$NORC DD DUMMY
5. After applying the DD, restart the address space.

Task 7: To stop the previous agent

Run the following command:

(Optional) Task 8: To upgrade Cloud Data Sets

To upgrade Cloud Data sets, see Upgrading-Cloud-Data-Sets.

Task 9: To perform RACF related tasks

1. If you are using the PROGRAM class, define the BMC AMI Cloud loadlib as program-controlled

   # Only if class PROGRAM is active
   RALT PROGRAM * ADDMEM('SYS2.MODEL9.V411.LOADLIB'//NOPADCHK)
   SETR WHEN(PROGRAM) REFRESH

2. ​​​​We have changed the SAF profiles that control the UI Alter command to align with CLI profiles. You must redefine your user permissions accordingly.  

   # Delete the old profiles
   RDELETE XFACILIT M9.UI.ARCHIVE.ALTER UACC(NONE)          
   RDELETE XFACILIT M9.UI.ARCHIVE.ALTER.PURGE UACC(NONE)    
   RDELETE XFACILIT M9.UI.CDS.ALTER UACC(NONE)              
   RDELETE XFACILIT M9.UI.CDS.ALTER.PURGE UACC(NONE)        
   RDELETE XFACILIT M9.UI.BACKUP.ALTER UACC(NONE)           
   RDELETE XFACILIT M9.UI.BACKUP.ALTER.PURGE UACC(NONE)
   
   # Define the new profiles
   RDEFINE XFACILIT M9.UI.ALTER.ARCHIVE UACC(NONE)         
   RDEFINE XFACILIT M9.UI.ALTER.ARCHIVE.PURGE UACC(NONE)   
   RDEFINE XFACILIT M9.UI.ALTER.CDS UACC(NONE)             
   RDEFINE XFACILIT M9.UI.ALTER.CDS.PURGE UACC(NONE)       
   RDEFINE XFACILIT M9.UI.ALTER.BACKUP UACC(NONE)          
   RDEFINE XFACILIT M9.UI.ALTER.BACKUP.PURGE UACC(NONE)  
   
   # Grant permissions to the new profiles based on the old ones
   PERMIT M9.UI.ALTER.ARCHIVE           +               
       CL(XFACILIT) ID(##YOUR_USER/GROUP##) ACC(READ)   
   PERMIT M9.UI.ALTER.ARCHIVE.PURGE           +         
       CL(XFACILIT) ID(##YOUR_USER/GROUP##) ACC(READ)   
   PERMIT M9.UI.ALTER.CDS           +                   
       CL(XFACILIT) ID(##YOUR_USER/GROUP##) ACC(READ)   
   PERMIT M9.UI.ALTER.CDS.PURGE           +             
       CL(XFACILIT) ID(##YOUR_USER/GROUP##) ACC(READ)   
   PERMIT M9.UI.ALTER.BACKUP           +                
       CL(XFACILIT) ID(##YOUR_USER/GROUP##) ACC(READ)   
   PERMIT M9.UI.ALTER.BACKUP.PURGE           +            

Task 10: To start the agent

1. Start the agent from any console by issuing the following command: 

   S M9AGENT

2. Verify that the agent was started successfully. The following messages should appear: 

   ZM91002I MODEL9 BACKUP AGENT VERSION 4.1.1 INITIALIZING
   ZM91000I MODEL9 BACKUP AGENT INITIALIZED

3. Verify that the agent is connected to the object storage by searching for the following message in STDOUT:

   Object store connectivity has been established successfully 

   Tip

   The message is broken into two lines. Search for the word successfully.