Upgrade z/VM 6.4 to 7.2 for 2nd member of SSI
search cancel

Upgrade z/VM 6.4 to 7.2 for 2nd member of SSI

book

Article ID: 392594

calendar_today

Updated On:

Products

VM:Secure for z/VM

Issue/Introduction

Upgrade in Place (UIP) on a SSI enabled system.

Have read "Upgrade z/VM 6.4 or z/VM 7.1 to z/VM 7.2" chapter and it seems to refer only to UIP on the first member of the SSI.

Need to Upgrade z/VM 6.4 to 7.2 for 2nd member of SSI not the first member.

See IBM zVM720 Installation Guide

 

Environment

Product: VM:Secure for z/VM

Resolution

The way Upgrade In Place (UIP) works is to:

  1. Install the Work system to get the new Release Volumes integrated into the SSI system you are upgrading.
  2. Integrate the new Release Volumes into the 1st SSI member you are upgrading:
    1. Add the new Release Volume UserIDs and MDISK into your User Directory.
    2. Make any other release specific directory changes; Update MDISK links to point to the new release product disks (MAINT640 --> MAINT720, 6VMTCP40 --> 7VMTCP20, etc.)
    3. Rework your Local Modifications to incorporate them into the new release CPLOAD MODULE (VM:Secure, V/Seg) and PMAINT CF0 PARM Disk (VMNDLK64 --> VMNDLK72, VMV640 --> VMV720); AND update the SYSTEM CONFIG file CPXLOAD reference(s) for THIS SSI Member to load these new release TEXT file(s) (you change the SYSTEM CONFIG entries for the other SSI members at the time you upgrade those members).
    4. Deploy the updated CPLOAD MODULE with local modifications performed in #3 above to the RES volume of the 1st SSI member.
    5. Re-IPL the 1st SSI member upgraded to the new  release.
    6. Complete any final items you are instructed to do in PART 4.
  3. Start PART 5 for the next SSI Member. Essentially what PART 5 does is:
    1. Updates the System UserID subconfigs to point to the new release software disks (TCPIP-2, RSCS-2, etc.).
    2. Deploys the already upgraded (including the Local Modifications you performed in Step 2, #3 above) release CPLOAD MODULE to THIS Members RES volume. Essentially it run PUT2PROD for this 2nd, 3rd, etc. SSI Member you are upgrading.
    3.  NOTE! You must be sure to update the SYSTEM CONFIG file CPXLOAD reference(s) for THIS SSI Member before you IPL it with the new release!

So, in PART 4, you do all the rebuilding of the CPLOAD MODULE and put the new Broadcom release specific TEXT files that are CPXLOADED on the PMAINT CF0 before the UPI procedure performs the PUT2PROD for the 1st SSI Member you are upgrading.

Then, in PART 5, you are essentially just running a PUT2PROD with the new release materials that you have already built in PART 4 to the RES volume of the 2nd, 3rd, etc. SSI Member. 

Need to remember to do is update the SYSTEM CONFIG file CPXLOAD references for the 2nd, 3rd, etc. SSI Member before you IPL each of those members when instructed to do so in PART 5.