Administration Guide › Upgrade in Place Installation

Upgrade in Place Installation

This chapter documents the steps to follow when using the process documented in the section on Upgrade Installation in the z/VM Installation Guide. This process is new in z.VM 6.3.0.

Upgrading z/VM 6.2.0 to z/VM 6.3.0 (CA VM:Secure)

Follow the steps in this section to upgrade z/VM 6.2.0 to z/VM 6.3.0:

Add an ACCOUNT User Exit to CA VM:Secure that lets MIGMAINT add any account code.
The exit EXEC file can be as simple as the following example:
```
/* MYACTXIT EXEC * /
Exit 0
```
Place the file on the VMSECURE A-disk, and add this line to your PRODUCT CONFIG file (substituting your exit filename):
```
USEREXIT ACCOUNT MYACTXIT EXEC
```
Note: You can remove this exit after the upgrade.
Verify that all DASD volumes in the 6.2.0 system which will hold minidisks created during the upgrade process are configured in the DASD CONFIG file.
Note: The volumes are specified on the worksheets you fill in by following the IBM procedures in the Plan your Installation Upgrade chapter of the z/VM Installation Guide Version 6 Release 3.
Add GRANT *ALL TO MIGMAINT to the AUTHORIZ CONFIG file.

Issue the VMSECURE RULES SYSTEM command and make sure that these entries are present:

ACCEPT MIGMAINT LINK * * ( NOPASS
ACCEPT MAINT620 LINK * * ( NOPASS
ACCEPT BLDSEG   LINK * * ( NOPASS
ACCEPT BLDNUC   LINK * * ( NOPASS
ACCEPT BLDCMS   LINK * * ( NOPASS

Run these steps in the following chapters of the z/VM Installation Guide Version 6 Release 3:
1. Chapter 20: "Plan Your Upgrade Installation"
2. Chapter 21: "Set Up For Your Upgrade Installation"
3. Chapter 22: "Install a z/VM V6.3 Work System For Your Upgrade Installation".
Perform these changes in Chapter 23, "Generate the STAGE1 Changes File":
1. Before you issue the INSTUPGR STAGE1 ( PRIME command, LINK and ACCESS the CA VM:Secure PUBLIC disk at a filemode earlier in the search order than the Y-disk, unless you already deployed the PUBLIC files to the Y-disk.
2. Issue the following command:
```
INSTUPGR STAGE1 ( PRIME
```
  If errors occur, CA VM:Secure logs any problems in the following file:
```
UPGDMIXT $LOGFILE E
```
  If CA VM:Secure reports any problems, correct them and reissue INSTUPGR.
Perform these changes in Chapter 24, "Update Your Current System With the STAGE1 Changes":
1. Before you issue the INSTUPGR STAGE1 ( COMMIT command, examine files with filetype $DIRADD$, generated by the STAGE1 PRIME processing.
2. Look at all MDISK statements to determine the volume serial numbers of all 630RLx volumes where minidisks exist.
3. Add all the 630RLx volumes to the CA VM:Secure DASD CONFIG file so that minidisks on those volumes can be allocated.
4. Issue the CONFIG DASD product command to configure the 630RLx volumes in the same allocation subpool containing the 620RLx volumes.
  Add an IGNORE statement in the DASD CONFIG file so that any full minidisks in the MAINT630 directory entry can be created.
5. Issue VMSECURE CONFIG DASD and add a statement like the following example:
```
IGNORE MAINT630 131
```
6. Check the MAINT630 $DIRADD$ file on the MIGMAINT 2CF0 disk to verify that all full volume minidisks have an IGNORE statement in the DASD CONFIG file.
7. LINK and ACCESS the CA VM:Secure PUBLIC disk at a filemode earlier in the search order than the Y-disk, unless you already deployed the PUBLIC files to the Y-disk.
8. Issue the following command:
```
INSTUPGR STAGE1 ( COMMIT
```
  If errors occur, CA VM:Secure logs all problems in the following file:
```
UPGDMIXT $LOGFILE E
```
  If CA VM:Secure reports any problems, correct them and re-issue INSTUPGR.
Perform these changes in Chapter 25, "Finish the STAGE1 Upgrade":
1. Issue VMSECURE RULES SYSTEM and add the following line:
```
ACCEPT MAINT630 LINK * * ( NOPASS
```
2. Rework your local modifications, including the CP components added to your system by CA VM:Secure. Update the CA VM:Secure CP components by using the HCPxxx TEXT files generated by the command:
```
VMXCPG ZVM630.
```
Note: Refer to the procedures documented in the Rules Facility Guide to add the newer CP components to your VMSES CP component LOCALMOD minidisk or directory.
Run the steps in Chapter 26, "Stop Your Production Workload And Backup Your System."
Perform these changes from Chapter 27, "Generate the STAGE2 Changes File":
1. Before you issue the INSTUPGR STAGE2 ( PRIME command, LINK and ACCESS the CA VM:Secure PUBLIC disk at a filemode earlier in the search order than the Y-disk, unless you already deployed the PUBLIC files to the Y-disk.
2. Issue the following command:
```
INSTUPGR STAGE2 ( PRIME
```
  If errors occur, CA VM:Secure logs any problems in the following file:
```
UPGDMIXT $LOGFILE E
```
  If CA VM:Secure reports any problems, correct them and re-issue INSTUPGR.
Perform these changes in Chapter 28, "Update Your Current System With the STAGE2 Changes":
1. LINK and ACCESS the CA VM:Secure PUBLIC disk at a filemode earlier in the search order than the Y-disk, unless you already deployed the PUBLIC files to the Y-disk before issuing:
```
INSTUPGR STAGE2 ( COMMIT
```
2. After the IPL 190 step, LINK and ACCESS the CA VM:Secure PUBLIC disk at a filemode in front of the Y-disk, unless you already deployed the PUBLIC files to the Y-disk before reissuing:
```
INSTUPGR STAGE2 ( COMMIT
```
  If errors occur, CA VM:Secure logs any problems in the following file:
```
UPGDMIXT $LOGFILE E
```
  If CA VM:Secure reports any problems, correct them and reissue INSTUPGR.
Perform the remaining steps in the IBM documentation.