Upgrading Cloud Data Sets


Related topic

Cloud Data Sets

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

Warning
Important

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

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. Warning
    Important

    Skip this step if you are upgrading from version 4.2.01

    Stop the M9VDEV 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.

Warning

Important

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

(Optional) Task 2: To enable CDS compaction toleration

Warning
Important

You can skip this task and perform it after installing CDS, but compaction toleration is not available until you complete the task. If you skip it, CDS processes requiring compaction will fail, compaction requests will be ignored, and the data will be compressed according to the worker setup. 

If you perform this task at a later stage, you must vary the CDS virtual devices offline by using the V xxxx-yyyy,OFFLINE command before starting the procedure. 

For CDS to tolerate hardware compaction, you must convert the CDS devices from 3480 to 3480X by enabling the COMPACT parameter in IODF. All the devices in the MTL library must be of the same type. To convert the devices, perform the following procedure:

  1. Open the Hardware Configuration (HCD) view.
  2. Select option 1 and press Enter to open the Define, Modify, or View Configuration Data view. 
  3. On the Define, Modify, or View Configuration Data view, select option 5 for I/O Data and press Enter

    +---------------- Define, Modify, or View Configuration Data -----------------+
    |                                                                 Row 1 of 10 |
    |                                                                             |
    |     Select type of object to define, modify, or view data.                  |
    |                                                                             |
    |      5  1. Operating system configurations                                  |
    |              consoles                                                       |
    |              system-defined generics                                        |
    |              EDTs                                                           |
    |                esoterics                                                    |
    |                user-modified generics                                       |
    |          2. Switches                                                        |
    |               ports                                                         |
    |               switch configurations                                         |
    |                 port matrix                                                 |
    |          3. Processors                                                      |
    |               channel subsystems                                            |
    |                 partitions                                                  |
    |                 channel paths                                               |
    |               PCIe functions                                                |
    |          4. Control units                                                   |
    |          5. I/O devices                                                     |
    |          6. Discovered new and changed control units and I/O devices        |
    |   F1=Help    F2=Split   F3=Exit    F9=Swap   F12=Cancel                     |
    +-----------------------------------------------------------------------------+
  4. On the I/O Device List view, type l deviceName in the command line to select the device for which you want to turn on compaction and press Enter

    . --------------------------------------------------------------------------     .
    .                              I/O Device List        Row 1 of 937 More:       > .
    .                                                                                .
    . Select one or more devices, then press Enter. To add, use F11.                 .
    .                                                                                .
    .   ----------Device------ --#--- --------Control Unit Numbers + --------        .
    . / Number   Type +        CSS OS 1--- 2--- 3--- 4--- 5--- 6--- 7--- 8---        .
    . _ 0031     2032          4      0031 ____ ____ ____ ____ ____ ____ ____        .
    . _ 0033     2032          3      0033 ____ ____ ____ ____ ____ ____ ____        .
    . _ 0101     2032               8 ____ ____ ____ ____ ____ ____ ____ ____        .
    . _ 0102     2032               7 ____ ____ ____ ____ ____ ____ ____ ____        .
    . _ 01C0,20  3390          1    7 3000 ____ ____ ____ ____ ____ ____ ____        .
    . _ 001D4,4  3390          1    7 3000 ____ ____ ____ ____ ____ ____ ____        .
    . _ 01E0,32  3390          1    6 3010 ____ ____ ____ ____ ____ ____ ____        .
    . _ 0200,16  OSA                4 ____ ____ ____ ____ ____ ____ ____ ____        .
    . _ 0200,32  3390          1    6 3000 ____ ____ ____ ____ ____ ____ ____        .  
    . _ 0220,6  3390           1    7 3000 ____ ____ ____ ____ ____ ____ ____        .  
    . _ 0226     3390          1    7 3000 ____ ____ ____ ____ ____ ____ ____        .  
    . _ 0230,16  3390          1    6 3000 ____ ____ ____ ____ ____ ____ ____        .  
    . _ 0260,32  3390          1    6 3010 ____ ____ ____ ____ ____ ____ ____        .  
    . _ 0280,32  3390          1    6 3010 ____ ____ ____ ____ ____ ____ ____        .
    .                                                                                .
    . Command ===> l b000_____________________________________ Scroll ===> CSR       .
    .  F1=Help      F2=Split      F3=Exit     F4=Prompt     F5=Reset    F7=Backward  .
    . ------------------------------------------------------------------------------ . 
  5. To modify the existing definition, type next to the device number and press Enter.
  6. On the Change Device Definition view, press Enter. On the following Device/Processor Definition view, press Enter again.
  7. On the Define Device to Operating System Configuration view, type s next to the configuration for which you want to turn on compaction and press Enter.
  8. On the Define Device Parameters/Features view, type Yes in the COMPACT field and press Enter.

    +-------------------- Define Device Parameters / Features --------------------+
    |                                                                 Row 1 of 10 |
    |                                                                             |
    | Specify or revise the values below.                                         |
    |                                                                             |
    | Configuration ID . : MOD9         MOD9 IODF                                 |
    | Device number  . . : 1100         Number of devices  : 16                   |
    | Device type  . . . : 3480                                                   |
    |                                                                             |
    | Parameter/                                                                  |
    | Feature    Value +          R Description                                   |
    | OFFLINE    Yes                Device considered online or offline at IPL    |
    | DYNAMIC    Yes                Device supports dynamic configuration         |
    | LOCANY     Yes                UCB can reside in 31 bit storage              |
    | LIBRARY    NO                 Device supports auto tape library             |
    | AUTOSWITCH NO                 Device is automatically switchable            |
    | LIBRARY-ID 99999___________   5 digit library serial number                 |
    | LIBPORT-ID 01______________   2 digit library string ID (port number)       |
    | MTL        Yes                Manual Tape Library (NOTE: PORTID LIMIT=32)   |
    | SHARABLE   No                 Device is Sharable between systems            |
    | COMPACT    Yes                Compaction                                    |
    +-----------------------------------------------------------------------------+
  9. Generate a new production IODF.
  10. Activate the new IODF to apply both software and hardware changes.

Task 3: To install Cloud Data Sets version 5.0.01

  1. Extract the BMC AMI Cloud CDS binaries: 

    Warning
    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 doesn't 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.

      Warning

      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 don't 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-5.0.1.tar "model9-data-vault-zos-package-v5.0.1/model9-m9cdswk-v5.0.1.tar"
      tar -xpf model9-data-vault-zos-package-5.0.1.tar "model9-data-vault-zos-package-v5.0.1/model9-m9env-v5.0.1.tar"

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

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

      • /usr/lpp/model9/binaries/model9-m9env-v5.0.1
      • /usr/lpp/model9/binaries/model9-m9cdswk-v5.0.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-v5.0.1/installation
    2. Edit and run the M9CDSWK installation job.
      Sample JCL is available in the following path:
      /usr/lpp/model9/binaries/m9cdswk-v5.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.V050001.LOADLIB,VOLUME=loadvolser
      /SETPROG APF,ADD,DSNAME=hlq.M9CDSWK.V050001.LOADLIB,VOLUME=loadvolser
    4. To APF-authorize after each IPL, add these statements to your PROGxx member.
  3. Copy the 4.r.m properties files:

    ENVIRONMENT=ZM9P
    cd /usr/lpp/model9/$ENVIRONMENT/config/
    cp ./m9env-v4.r.m.properties ./m9env-v5.0.1.properties
    cp ./m9cdswk-v4.r.m.properties ./m9cdswk-v5.0.1.properties 
  4. If you are upgrading from version 4.2.00, in the m9env.properties file, update the cds.sio.volume-prefix parameter to cds.volume-prefix. Otherwise, skip this step.

  5. Customize the BMC AMI Cloud CDS PROCs:

    Error
    Warning

    Version 5.0.01 has significant changes in the STC JCL. We recommend copying the new JCL from the samplib and modifying it, rather than modifying your existing JCL.

    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.V050001.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.V050001.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*

BMC AMI Cloud Data and BMC AMI Cloud Vault 5.0