Performing the Cloud Data Sets upgrade from version 3.3.00

This topic describes how to upgrade Cloud Data Sets (CDSs).

Before you begin

See Preparing-to-upgrade-Cloud-Data-Sets-from-version-3-3-00.

Task 1: To remove Cloud Data Sets version 3.3.00 from your system

Vary the CDS virtual devices offline by using the following command:
V xxxx-yyyy,OFFLINE
Make sure that all devices are OFFLINE by using the following command:
D U,,,xxxx,nn
Example
UNIT TYPE STATUS
0570 348M F-NRD
0571 348M F-NRD
0572 348M F-NRD
0573 348M F-NRD
0574 348M F-NRD
0575 348M F-NRD
0576 348M F-NRD
0577 348M F-NRD
0578 348M F-NRD
0579 348M F-NRD
057A 348M F-NRD
057B 348M F-NRD
057C 348M F-NRD
057D 348M F-NRD
057E 348M F-NRD
057F 348M F-NRD
Stop the VDEV started task by running the following command:
P M9VDEV
Warning
If the vary offline step did not complete successfully, the VDEV started task does not shut down.
Uninstall CDS by running the following command:
S M9UNICDS
Important
Make sure that you are using the version 3.3.00 M9UNICDS.
Remove OCE exit definitions by using the SETPROG command:
SETPROG EXIT,DELETE,EXITNAME=OCE_VOLUMEMOUNT,MOD=ZM9OCEX4
SETPROG EXIT,DELETE,EXITNAME=OCE_FILESTART,MOD=ZM9OCEX4
SETPROG EXIT,DELETE,EXITNAME=OCE_FILEEND,MOD=ZM9OCEX4
SETPROG EXIT,DELETE,EXITNAME=OCE_FILEVALIDATE,MOD=ZM9OCEX4
SETPROG EXIT,DELETE,EXITNAME=OCE_LABELANOMALY,MOD=ZM9OCEX4

CDS version 3.3.00 is removed from your system.

Important

Make sure that you remove CDS version 3.3.00 from your system automation.

Task 2: To install Cloud Data Sets version 4.0.01

Extract the BMC AMI Cloud CDS binaries:
Important
Only users with the following FACILITY class permissions can extract the CDS files:
- BPX.FILEATTR.APF ACC(READ)
- BPX.FILEATTR.PROGCTL ACC(READ)
- BPX.FILEATTR.SHARELIB ACC(READ)
If the user does not have these permissions, the extract succeeds, but the binaries might be corrupted.

1. Use an FTP utility to upload the product package installation .tar file to the BMC AMI Cloud directory.
  Important
  - We recommend using a passive FTP mode (if supported).
  - You must upload the .tar file in binary mode.
  - If you have already uploaded the product package when installing the agent, you do not need to upload the package for the CDS installation.
2. Use the tar command in the z/OS UNIX shell to extract the CDS.
  TSO OMVS
  su
  cd /usr/lpp/model9
  tar -xpf model9-data-vault-zos-package-4.0.1.tar "model9-data-vault-zos-package-v4.0.1/model9-m9cdswk-v4.0.1.tar"
  tar -xpf model9-data-vault-zos-package-4.0.1.tar "model9-data-vault-zos-package-v4.0.1/model9-m9env-v4.0.1.tar"
  Important
  The agent is shipped within the model9-data-vault-zos-package-4.0.1.tar file. For more information about installing the agent, see Installing-the-BMC-AMI-Cloud-agent.
3. Use the tar command again to extract the CDS component files.
  TSO OMVS
  su
  cd /usr/lpp/model9
  mkdir binaries
  cd model9-data-vault-zos-package-v4.0.1
  tar -xpf model9-m9env-v4.0.1.tar -C ../binaries/
  tar -xpf model9-m9cdswk-v4.0.1.tar -C ../binaries/
  The extraction process generates the following directories containing the CDS binaries:
  - /usr/lpp/model9/binaries/model9-m9env-v4.0.1
  - /usr/lpp/model9/binaries/model9-m9cdswk-v4.0.1
Create and populate the CDS LOADLIB:
1. Edit and run the M9ENV installation job.
  Sample JCL is available in the following path:
  /usr/lpp/model9/binaries/m9env-v4.0.1/installation
2. Edit and run the M9CDSWK installation job.
  Sample JCL is available in the following path:
  /usr/lpp/model9/binaries/m9cdswk-v4.0.1/installation
3. APF-authorize the LOADLIBs that were created in the preceding steps, by using the following command:
  /SETPROG APF,ADD,DSNAME=hlq.M9ENV.V040001.LOADLIB,VOLUME=loadvolser
  /SETPROG APF,ADD,DSNAME=hlq.M9CDSWK.V040001.LOADLIB,VOLUME=loadvolser
4. To APF-authorize after each IPL, add these statements to your PROGxx member.
Create and copy the BMC AMI Cloud CDS sample configuration directory by using the following commands:
ENVIRONMENT=ZM9P
mkdir /usr/lpp/model9/$ENVIRONMENT/
cd /usr/lpp/model9/$ENVIRONMENT/
mkdir diag config logs
chmod 777 logs
cp ../binaries/model9-m9env-v4.0.1/config/m9env-v4.0.1.properties ./config/
cp ../binaries/model9-m9env-v4.0.1/config/m9env-logback.xml ./config/
cp ../binaries/model9-m9cdswk-v4.0.1/config/m9cdswk-v4.0.1.properties ./config/
cp ../binaries/model9-m9cdswk-v4.0.1/config/m9cdswk-logback.xml ./config/
cp ../binaries/model9-m9env-v4.0.1/config/licenses.txt ./config/
chtag -t -c ISO8859-1 ./config/licenses.txt
Update the BMC AMI Cloud CDS configuration files in /usr/lpp/model9/$ENVIRONMENT/config. (For information about CDS parameters, see BMC-AMI-Cloud-Data-Sets-parameters.)
1. M9ENV properties file:
  units.address-range.from=<device-start-range>
  units.address-range.to=<device-end-range>
2. M9CDSWK properties file:
  Warning
  migrations.cds-links-migration-v400-enabled=true is required to enable the M9CDSWK to use version 3 format CDSs. Make sure that you set it to false as part of the link migration process documented in Task 2: To convert the CDS files format.
  jclouds.api-id=s3
  jclouds.endpoint-url=<Storage URL or IP address>
  jclouds.bucket=<container name>
  jclouds.user=<storage access key>
  jclouds.password=<storage secret key>
  units.address-ranges[0].from=<worker-device-start-range>
  units.address-ranges[0].to=<worker-device-end-range>
  migrations.cds-links-migration-v400-enabled=true
3. Update the license as displayed in the following sample. The license is in ASCII format. You need to edit it from ISPF option 3.17.
  Important
  Because the file is in ASCII format, all comments must start with a # sign regardless of your code page.
  Command ===> Scroll ===> CSR
  ****** ***************************** Top of Data ******************************
  000001 ########################################################################
  000002 # (c) Copyright 2025 BMC Software, Inc.
  000003 ########################################################################
  000004 #
  000005 # Model9 Licenses
  000006 #
  000007 # Place each license on its own line.
  000008 # Lines beginning with '#' are ignored, as are empty lines.
  000009 #

Customize the BMC AMI Cloud CDS PROCs:

Copy the sample JCL for M9VDEV, M9ENV, and M9CDSWK from the SAMPLIB PDSs to local PROCLIB members.
Important
You must replace the old M9VDEV JCL with the new one because they are not the same.

Update the following variables in the M9VDEV and M9ENV JCLs:

Variable	Update	Default value
ENV	Environment name	ZM9P
STEPLIB DD	BMC AMI Cloud (M9ENV or M9VDEV) installation LOADLIB	SYS2.MODEL9.V040001.M9ENV.LOADLIB
M9DIR	BMC AMI Cloud CDS environment home	/usr/lpp/model9/
TIMEZONE	CDS time zone	America/New_York
HEAPSIZE	Heap size setting	64 MB
JAVAHOME	64-bit Java home path	/usr/lpp/java/current_64

Update the following variables in the M9CDSWK JCL:

Variable	Update	Default value
STEPLIB DD	BMC AMI Cloud M9CDSWK installation LOADLIB	SYS2.MODEL9.V040001.M9CDSWK.LOADLIB
M9DIR	BMC AMI Cloud CDS environment home	/usr/lpp/model9/
TIMEZONE	CDS time zone	America/New_York
HEAPSIZE	Heap size setting	3 GB
ENV	Environment name	ZM9P
NAME	Worker name	M9CDSWK
TCPIP	TCP/IP stack used by the M9CDSWK	TCPIP
JAVAHOME	64-bit Java home path	/usr/lpp/java/current_64

Start the BMC AMI Cloud CDS PROCs:
1. Start the M9ENV STC by using the following command:
  S M9ENV
2. Start the M9VDEV STC by using the following command:
  S M9VDEV
3. Start the M9CDSWK STC by using the following command:
  S M9CDSWK
4. Start the devices and MTL.

Where to go from here

Converting-the-CDS-files-format.