Performing Cloud Data Sets installation

Perform the following tasks to activate Cloud Data Sets (CDSs). For CDS requirements, see z-OS-requirements. 

Task 1: To extract the BMC AMI Cloud CDS binaries

Related topic

Installing-Cloud-Data-Sets

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 BMC AMI Cloud agent’s 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 for agent install you do not need to upload the package for the CDS install. 

  2. Use the tar command in the z/OS UNIX shell to extract the CDS files.

    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-package-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-package-v4.0.1.tar"

  3. Use the tar command again to extract the CDS component files. During the extraction, all CDS files are saved in two directories. 
    The M9ENV and M9CDSWK directories are created in the following binaries path:

    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

Task 2: To 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/model9-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/model9-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 the above mentioned statements to your PROGxx member. 

Task 3: To create and populate the BMC AMI Cloud CDS configuration directories

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

Task 4: To update the BMC AMI Cloud CDS configuration

Before you start the CDS started tasks, perform the following steps: 

  1. Update the configuration files located in /usr/lpp/model9/$ENVIRONMENT/config. For information about the CDS parameters, see BMC-AMI-Cloud-Data-Sets-parameters.
    • In M9ENV properties, update the following parameters:
      • units.address-range.from=<device-start-range>
      • units.address-range.to=<device-end-range>
         
    • In M9CDSWK properties, update the following parameters:
      • 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> 

        Important

        By default, the worker tries to verify the storage certificate. You must specify jclouds.verify-endpoint-certificate=false until you follow the process described in Enabling-trust-between-the-worker-and-the-object-storage.

  2. Update the license as displayed in the following license file 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 # 

Task 5: To customize the BMC AMI Cloud CDS PROCs

Copy the sample JCL for M9VDEV, M9ENV, and M9CDSWK from the SAMPLIB PDSs to a local PROCLIB.

  1.   Update the following variables in the M9ENV JCL:

    Variable

    Update

    Default value

    ENV

    Environment name

    ZM9P

    STEPLIB DD

    BMC AMI Cloud M9ENV installation LOADLIB

      SYS2.MODEL9.M9ENV.V040001.LOADLIB  

    M9DIR

    BMC AMI Cloud CDS environment home

    /usr/lpp/model9/

    TIMEZONE

    CDS time zone

    America/New_York

    HEAPSIZE

    Heap size setting

    64 MB

  2. Update the following variables in the M9VDEV JCL:

    Variable

    Update

    Default value

    ENV

    Environment name

    ZM9P

    STEPLIB DD

    BMC AMI Cloud M9ENV installation LOADLIB

      SYS2.MODEL9.M9ENV.V040001.LOADLIB  

    CHPID

    Only applicable if you are running your z/OS system as zVM GUEST.

    00

    SCHNOOnly applicable if you are running your z/OS system as zVM GUEST.

    0000

    DEV 

    Virtual tape device range

    The value must match the M9ENV range. 

    B000-B03F

    VOLPREFTape volser prefixMC
    SGSMS storage group name used by the librarySGAMICDS
    MBLKMaximum block size supported by VDEV00262144
    OBLKOptimal block size supported by VDEV00262144
    Important

    While the SMS storage group can be of any length, the value of the JCL SG variable must be exactly 8 characters. If needed, pad it with trailing underscores. For example, SG='M9CDS_'. 

    Warning

    Do not change the CHPID and SCHNO parameters without technical advice from BMC. 

  3. Update the following variables in the M9CDSWK JCL:

    Variable

    Update

    Default value

    STEPLIB DD

    BMC AMI Cloud M9CDSWK installation LOADLIB

    SYS2.MODEL9.M9CDSWK.V040001.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

Task 6: To start the BMC AMI Cloud CDS PROCs

Perform the following steps to start the 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. Vary the devices and MTL online.

To stop the BMC AMI Cloud CDS PROCs

Perform the following steps to stop the CDS PROCs: 

  1. Vary the devices and MTL offline.

  2. Stop the M9CDSWK STC by using the following command: 

    P M9CDSWK

  3. Stop the M9VDEV STC by using the following command: 

    p M9VDEV

  4. Stop the M9ENV STC by using the following commands:

    f M9ENV,APPL=INTERCEPT STOP ALL
    p M9ENV

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*