Upgrade ZVM720, Subset CP:
This subset contains installation information for z/VM - CP
Version 7, Release 2, Modification 0.
Change Summary
DATE LAST
CHANGED SECTION
1. 22/03/23 INSTALLATION INFORMATION
2. 22/03/23 DOCUMENTATION CHANGES
3. YY/MM/DD GENERAL INFORMATION NO ENTRIES
4. 22/05/17 SERVICE RECOMMENDATIONS SEE 2301RSU
5. YY/MM/DD CROSS PRODUCT DEPENDENCIES NO ENTRIES
This section contains changes to the product's Program Directory.
and additional information which should be review before installing
the product. Please note the additional APARs required for older
z/VM releases when they are members of a mixed environment SSI cluster.
7. 22/03/23 UPGRADE INSTALL: INSTALL VMSES APAR BEFORE UPGRADING
Before upgrading from z/VM 7.1 to 7.2 you should install
and put into production the PTF for APAR VM66519 (UM35857).
This PTF was included on RSU 7105 (CP Service level 2101).
When this PTF is installed you should not need to perform
the actions outlined in item 1 below. There is no PTF for
z/VM 6.4 so you will need to perform the actions in item 1
when upgrading to z/VM 7.2.
After upgrading to 7.2 you should install the 7.2 PTF for
APAR VM66519 (UM35858). This PTF was included on z/VM 7.2
RSU 7203 (CP Service level 2102).
6. 21/07/21 Warning message during INSTUPGR STAGE2 (PRIME to ignore
If you use RACF and GCS on your system you may have copied
two RACF files, RPICDX LOADLIB and RPIGCS LOADLIB, to
the MAINT 193 minidisk. If you did, you might receive this
warning message when you run INSTUPGR STAGE2 (PRIME:
* The following files found on your MAINT 193 minidisk
* were not listed in the VM PARTCAT for prodid 7VMRAC10%RACF,
* but will be overwritten during COMMIT processing.
RPICDX LOADLIB
RPIGCS LOADLIB
You should ignore this message.
5. 21/02/17 Restricted device address for installation
When installing z/VM (any release, traditional or upgrade)
do not use device address 0000 for any of your installation
volume address. This address will result in an error when
loading the new release code to the installation volumes.
4. 21/01/26 Upgrade Install: Apply RACF-related APARs to DirMaint
If you are using RACF/VM and DirMaint on your system and
DirMaint is enabled to communicate with RACF (USE_RACF=
YES), before you begin your upgrade to z/VM 7.2.0, it is
recommended that you install the PTF for DirMaint APAR
VM66044 on your z/VM 6.4.0 or 7.1.0 system. The PTF
numbers are:
APAR PTF
VM66044 UV99364 for z/VM 6.4.0
UV99365 for z/VM 7.1.0
If you also have ESM logging enabled for DirMaint
(ESM_LOG_RECORDING_EXIT= DVHESMLR EXEC), it is recommended
that you install the PTF for DirMaint APAR VM66204:
APAR PTF
VM66204 UV99374 for z/VM 6.4.0
UV99376 for z/VM 7.1.0
After you have completed your upgrade it is recommended
that you install the PTF for DirMaint APAR VM66204 for z/VM
7.2.0 (PTF UV99376) on your z/VM 7.2.0 system.
3. 21/01/26 Upgrade Install and RACF/VM: Verify MAINT720 minidisk
access If you are using RACF/VM and DirMaint on your system
and DirMaint is enabled to communicate with RACF (USE_RACF=
YES) and if you are using or did use the upgrade
installation procedure to move to z/VM V7 R2, before
attempting to install any additional service, you should
verify that MAINT720 is not restricted to READ access for
any of the MAINT production minidisks. When the MAINT720
userid is added to your system the directory entry contains
read links to the following minidisks:
MAINT 190
MAINT 193
MAINT 19E
MAINT 19D
MAINT 402
DirMaint will instruct RACF to update the RACF profiles
for those minidisks and add MAINT720 with READ authority.
For security, this is working as designed. However,
MAINT720 must be able to link to all production minidisks
using link mode MR. You will need to either remove
the specific READ authority (so that the OPERATIONS
authority that MAINT720 should have will be in effect)
or change the specific authority to CONTROL (so that
MAINT720 can link to the disks with link mode MR.)
2. 21/01/26 Maximum size for installing z/VM on SCSI volumes
For z/VM V7 R2 and prior releases, the maximum volume
size for installing on SCSI volumes is 400GB.
1. 21/01/26 Upgrade Install and DirMaint: Need to purge reader files
If you are using the upgrade installation procedures and
you use DirMaint, before beginning Stage 2 of the upgrade
process, ensure that no extraneous reader files exist in
the virtual reader for the following user IDs:
BLDNNUC
BLDCMS
BLDSEG
BLDRACF
To verify that the virtual readers are clean, please log on
to each user ID and do the following:
Issue the command: QUERY FILES
You should see the message:
FILES: NO RDR, NO PRT, NO PUN
Ready; ...
If any reader files are cited, enter the command:
PURGE * RDR ALL
Log off the user ID.
This section outlines major errors in the product's published
documentation.
2. 22/03/23 Correction to"z/VM 7.2.0 Installation Guide":
In Chapter 17 "Finish the STAGE1 upgrade", Step 3 (page 178),
change substep 6 to the following:
6. If certain local modifications exist against RACF, RACF
objects need to be rebuilt.
a. If a local modification exists against RACF part
ICHRDSNT ASSEMBLE which changes the name of the primary
and/or backup RACF dataset, the following commands must
be run to rebuild the objects built from the updated
ICHRDSNT part:
VMFSETUP SERVP2P RACF
VMFBLD PPF SERVP2P RACF RPIBL505 ICHRDSNT (ALL
VMFBLD PPF SERVP2P RACF RPIBLLNK ICHRDSNT (ALL
b. Certain RACF exits do not appear as local
modifications, but they need to be rebuilt before
continuing.
- If no TXT00000 files exist on the RACF local
modification disk (7VMRAC20 2C2 or
VMPSFS:7VMRAC20.RACF.SAMPLE), skip to substep 7 on
page 178.
- If TXT00000 files do exist on the RACF local
modification disk (7VMRAC20 2C2 or
VMPSFS:7VMRAC20.RACF.SAMPLE), perform a RACF build:
VMFSETUP SERVP2P RACF
VMFBLD PPF SERVP2P RACF RPIBLLPA (ALL
1. 21/07/14 Corrections for "z/VM 720: Installation Guide"
The corrections are as follows:
- In Chapter 2, Step 3, Substep 9: all mention of 3390
volume size 11000 cylinders should be 11500 cylinders
- In Chapter 2, Step 3, substep 10: all mention of FBA
volume size 8.0 GB should be 8.5 GB
- In Chapter 12, Step 3, substep 4: all mention of FBA
volume size of 8.0 GB should be 8.5 GB
- In Chapter 12, Step 3, substep 4: all mention of 3390
volume size 11000 cylinders should be 11500 cylinders
- In Chapter 12, Step 7, substep 1: all mention of 3390
volume size 11000 cylinders should be 11500 cylinders
- In Chapter 12, Step 8, substep 1: all mention of FBA
volume size of 8.0 GB should be 8.5 GB
NO ENTRIES
1. 21/07/20 Corrections for "z/VM 720: Installation Guide"
The corrections are as follows:
- In Chapter 2, Step 3, Substep 9: all mention of 3390
volume size 11000 cylinders should be 11500 cylinders
- In Chapter 2, Step 3, substep 10: all mention of FBA
volume size 8.0 GB should be 8.5 GB
- In Chapter 12, Step 3, substep 4: all mention of FBA
volume size of 8.0 GB should be 8.5 GB
- In Chapter 12, Step 3, substep 4: all mention of 3390
volume size 11000 cylinders should be 11500 cylinders
- In Chapter 12, Step 7, substep 1: all mention of 3390
volume size 11000 cylinders should be 11500 cylinders
- In Chapter 12, Step 8, substep 1: all mention of FBA
volume size of 8.0 GB should be 8.5 GB
This section contains information that is dependent upon another
product other than this subset ID. It also contains information
dealing with migration and product coexistance.
1. YY/MM/DD INTERDEPENDENT PRODUCT:
PROBLEM:
USERS AFFECTED:
RECOMMENDATION: INSTALL XXXXXXX ON VOLID XXXX