Cloud Data Manager

Upgrading the Model9 agent

  1. The supported upgrade path is from release 1.8.x to 2.0.0. This documentation is relevant for upgrading from release 1.8.x only. If the installed release is older than that, refer to previous installation guides.

  2. Verify that the agent’s installation prerequisites are met, see Prerequisites for details.

Note

Ensure that there are no policies scheduled to run during the upgrade operation.

Step 1: Upload the agent TAR File to the installation directory

Use FTP or similar utility to upload the Model9 agent’s installation tar file to the Model9 agent’s installation directory. Use Passive Mode if supported by the FTP client. The tar file must be uploaded in binary mode, as shown in the following example:

$ ftp mf-lp1
Connected to mf-lp1.
220-FTPD1 IBM FTP CS V2R2 at mf-lp1, 06:20:40 on 2017-02-23.
220 Connection will not timeout.
Name (mf-lp1:m9user): m9u
331 Send password please.
Password:
230 M9U is logged on. Working directory is "M9U.".
Remote system type is MVS.
ftp> cd /usr/lpp/model9/
250 HFS directory /usr/lpp/model9/ is the current working directory
ftp> bin
200 Representation type is Image
ftp> put model9-v2.0.0_build_f3aba202-agent.tar
local: model9-v2.0.0_build_f3aba202-agent.tar remote: model9-v2.0.0_build_f3aba202-agent.tar
229 Entering Extended Passive Mode (|||1026|)
125 Storing data set /usr/lpp/model9/model9-v2.0.0_build_f3aba202-agent.tar
250 Transfer completed successfully.
xxxxxx bytes sent in 00:02 (1.95 MiB/s)
ftp> quit
221 Quit command received. Goodbye.

Step 2: 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:

su
cd /usr/lpp/model9/
tar -xpf model9-v2.0.0_build_f3aba202-agent.tar
rm agent
ln -s model9-v2.0.0_build_f3aba202-agent agent

Step 3: Copy the Model9 libraries from USS to PDS and modify

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

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

Modify M9AGENT:

Update

Description

DD STEPLIB

Model9 installation LOADLIB

PWD environment variable

Model9 agent’s installation path

Optional parameters for M9AGENT:

Update

Description

CONF_HOME environment variable

Model9 agent’s configuration directory path

Use the CONF_HOME parameter for activating more than one agent in the same LPAR. The parameter will allow the agents to use the same Model9 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 Model9 complex. However, additional agents in the same LPAR may be required if:

  • Using a sub-plex

  • Running both development and production environments

  • 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:

//STDENV DD *
export PWD=/usr/lpp/model9/agent
export CONF_HOME=$PWD/../conf
export ENV=agent
. $PWD/scripts/stdenv-main.sh
//

Modify M9SAPI:

Update

Description

M9PATH

Model9 agent’s installation path

Modify M9LIFECY:

Update

Description

DD STEPLIB

Model9 installation LOADLIB

PWD environment variable

Model9 agent’s installation path

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

Step 4: Upgrade the Model9 Command Line Interface

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

fifodir = "/usr/lpp/model9/listener"
loaddir = "SYS2.MODEL9.V200.LOADLIB"

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

Step 5: Update the Model9 agent configuration

No actions necessary when upgrading from 1.8.x to 2.0.0.

Step 6: Upgrade automatic recall

  1. Use the sample JCL M9UNHOOK to uninstall the previous hook. The expected RC should be 0:

    S M9UNHOOK

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

  2. Replace the previously installed release and update the PROGxx configuration by adding the following statements:

    APF ADD DSNAME(SYS2.MODEL9.V200.LOADLIB) VOLUME(<VOLSER>)
    LPA ADD DSNAME(SYS2.MODEL9.V200.LOADLIB) MOD(ZM9CPTN)
    LPA ADD DSNAME(SYS2.MODEL9.V200.LOADLIB) MOD(ZM9S26X)
    1. Replace <VOLSER> with the relevant volume name.

    2. Use the SET PROG=XX operator command to apply the changes.

    3. Verify that the command has ended successfully.

    4. The hook and exit must be loaded to the Dynamic LPA in order for them to function correctly. Do not use MLPA or PLPA to load the modules.

  3. Install the feature by copying M9HOOK from the SAMPLIB PDS to a local PROCLIB member. Customize and activate the hook using the following command. The expected RC should be 0:

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

    //ZM9$NORC DD DUMMY
  5. Restart the address space after applying the DD.

Step 7: Define the Model9 loadlib as program controlled

If you are using the PROGRAM class, define the Model9 loadlib as program controlled.

# Only if class PROGRAM is active
RALT PROGRAM * ADDMEM('SYS2.MODEL9.V200.LOADLIB'//NOPADCHK)
PERMIT * CLASS(PROGRAM) ID(M9USER) ACC(READ)
SETR WHEN(PROGRAM) REFRESH

Step 8: Permit the agent

The Model9 agent is now using the IDCAMS DCOLLECT command and would also require an OMVS max threads setting increase. Permit the agent with the following:

PERMIT STGADMIN.IDC.DCOLLECT CL(FACILITY) ID(M9USER) ACC(READ)
ALTUSER M9USER OMVS(THREADSMAX(500))
SETROPTS RACLIST(FACILITY) REFRESH

Step 9: Start the agent

Stop the previous release agent:

P M9AGENT

Start the upgraded agent using the following command:

S M9AGENT

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

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