Upgrading Cloud Data Sets

  

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

Important

The supported upgrade path is from the previous two releases to the latest one. If the installed version is two or more releases older than the latest one, contact BMC Support.

Related topics

Cloud Data Sets

Task 1: To remove Cloud Data Sets version 4.x.xx from your system

  1. Vary the CDS virtual devices offline by using the following command:

    V xxxx-yyyy,OFFLINE

  2. 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

  3. Vary the MTL offline by using the following command: 

    V SMS,LIB(M9MTL),OFFLINE

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

    P M9CDSWK

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

    P M9VDEV

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

    F M9ENV,APPL=INTERCEPT STOP ALL
    P M9ENV

CDS version 4.x.xx is removed from your system.

Important

Make sure that you remove CDS version 4.x.xx from your system automation.

Task 2: To install Cloud Data Sets version 4.2.01

  1. 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.2.1.tar "model9-data-vault-zos-package-v4.2.1/model9-m9cdswk-v4.2.1.tar"
      tar -xpf model9-data-vault-zos-package-4.2.1.tar "model9-data-vault-zos-package-v4.2.1/model9-m9env-v4.2.1.tar"

      Important

      The agent is shipped within the model9-data-vault-zos-package-4.2.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
      cd model9-data-vault-zos-package-v4.2.1
      tar -xpf model9-m9env-v4.2.1.tar -C ../binaries/
      tar -xpf model9-m9cdswk-v4.2.1.tar -C ../binaries/

      The extraction process generates the following directories containing the CDS binaries: 

      • /usr/lpp/model9/binaries/model9-m9env-v4.2.1
      • /usr/lpp/model9/binaries/model9-m9cdswk-v4.2.1
         
  2. Create and populate the CDS LOADLIBs and SAMPLIBs:
    1. Edit and run the M9ENV installation job. 
      Sample JCL is available in the following path:
      /usr/lpp/model9/binaries/m9env-v4.2.1/installation
       
    2. Edit and run the M9CDSWK installation job.
      Sample JCL is available in the following path:
      /usr/lpp/model9/binaries/m9cdswk-v4.2.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.V040201.LOADLIB,VOLUME=loadvolser
      /SETPROG APF,ADD,DSNAME=hlq.M9CDSWK.V040201.LOADLIB,VOLUME=loadvolser
    4. To APF-authorize after each IPL, add these statements to your PROGxx member.

  3. Create the 4.2.01 properties files:

    ENVIRONMENT=ZM9P
    cd /usr/lpp/model9/$ENVIRONMENT/config/
    cp m9env-v4.2.1.properties ./m9env-v4.2.1.properties
    cp m9cdswk-v4.2.1.properties ./m9cdswk-v4.2.1.properties

  4. To enable CDS multi-volume support, add the following parameter to the m9env.properties file located in /usr/lpp/model9/$ENVIRONMENT/config: 

    cds.multi-volume.enabled=true

  5. We have moved the M9VDEV functionality into M9ENV address space. Make the following changes: 

    1. If applicable, remove M9VDEV from your automation processes.
    2. Rename M9VDEV to a different name in SYS1.PROCLIB to avoid accidental start.
    3. Use the M9VDEV values you have specified to update the m9env.properties file:
      • cds.sio.storage-group-name=storageGroupName
      • cds.sio.volume-prefix=volumePrefix

  6. Customize the BMC AMI Cloud CDS PROCs:

    Warning

    Note the changes to the following parameters:

    • We have changed the default of the jclouds.v4signatures parameter in M9CDSWK to false.
      If you need to use v4signatures, make sure that you have specified jclouds.v4signatures=true in the M9CDSWK.properties file.
    • We have changed the hlasm-logging.components.cds-vdev.wto.level parameter to hlasm-logging.components.cds-sio.wto.level 
    • We have changed the hlasm-logging.components.cds-vdev.wto.job-name to hlasm-logging.components.cds-sio.wto.job-name.
    1. Copy the sample JCL for M9ENV and M9CDSWK from the SAMPLIB PDSs to local PROCLIB members.
    2. Update the following variables in the M9CDSWK JCL: 

      Variable

      Update

      Default value

      STEPLIB DD

      BMC AMI Cloud M9CDSWK installation LOADLIB

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

      ​​​

    3. 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.V040201.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

    7. Start the BMC AMI Cloud CDS PROCs:

    1. Start the M9ENV STC by using the following command:

      S M9ENV

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

      S M9CDSWK

    3. Vary the CDS virtual devices online by using the following command:

      V xxxx-yyyy,ONLINE

    4. Vary the MTL online by using the following command: 

      V SMS,LIB(M9MTL),ONLINE

       

 

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