Search
Last Updated: 15 February 2024
The IBM Support Portal IBM Support Portal can be used to search for and access PSP bucket Upgrade and Subset information (for software and hardware topics). When using this facility, specify an applicable UPGRADE value for your search. More information and example search values are presented with the z/VM Preventive Service PSP Buckets topic.
Be certain to review the PSP Bucket for both installation information and additional program requirements. This information is presented in date order; review each entry in its entirety.
If you are planning or actively working on SSI cluster 730 system upgrades and need, or intend, to apply service as part of any post-upgrade actions, make note of the information that follows.
As noted in the z/VM: 730 Installation Guide, it is possible to apply service to a first-upgraded, SSI member 730 system in an SSI cluster, before any other member systems are upgraded. However, when this is done, specific actions can be required for certain z/VM components that have been updated with the applied RSU or PTF service. The components to which this consideration applies are: DirMaint, ICKDSF and (possibly) Language Environment (LE)
When service is applied that affects these components, the systemname $PRODS files that are produced for non-upgraded members — after having run the SERVICE command on the 730-upgraded member system — need to be adjusted. However, the need to do so currently is not documented.
The information needed is provided here, in supplemental form, as an update for:
z/VM: 730 Installation Guide Chapter 21. Finish your upgrade installation Step 7. Perform post-upgrade tasks; Item 8
It is possible that with the upgrade of this system, you want or need to install additional service for the new z/VM level. Possible reasons for doing so are:
You might have used the CHKAPARS utility (see Chapter 12, Step 4, substep "6" on page 115) to identify the service that you need to install. If you did not use CHKAPARS, you should review the service you have installed on your z/VM 7.1 or 7.2 system (since z/VM 7.3 became available), to see if your z/VM 7.3 system requires additional service.
If you intend to install additional service, you should obtain that as you normally would, and then log on to MAINT730 on your upgraded system to install it. After the service is installed, you can run PUT2PROD to put the new service into production on your upgraded system.
If service was applied for any of these products, this will be evident in the SERVICE message log, by the presence of message VMFSRV1233I (visible when VMFVIEW SERVICE is used), which cites those components updated with service.
If any of the DirMaint, LE or ICKDSF components were serviced, special handling of their put into production records (in the systemname $PRODS file) is needed, for those systems that are still running the old release of VM. A utility exec (UG$PRMOD UTLSAMP) is provided for this purpose.
To make use of the UG$PRMOD utility, do the following:
Confirm the 191 disk-resident UG$PRMOD BIN file has the correct attributes:
listfile ug$prmod bin a (isodate
The listed file should be reported as:
FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS DATE TIME UG$PRMOD BIN fmF 1024 nnnn yyyy-mm-dd hh:mm:ss
If the BIN file is a FIXed-format, LRECL 80 file, reformat the file accordingly using this CMS PIPELINE command:
pipe < ug$prmod bin a | fblock 1024 00 | > ug$prmod bin a f 1024
Again, confirm the 191 disk-resident UG$PRMOD BIN file has the correct attributes, using the previously used LISTFILE command.
After the subject file has the correct format, copy this file to create a UG$PRMOD EXEC file:
copyfile ug$prmod bin a = exec = (unpack olddate replace
Invoke the UG$PRMOD utility; specify the new z/VM level as an input operand:
ug$prmod 730
Make a note of any errors or warnings produced and resolve any problems. Upon completion of the utility, if a current systemname $PRODS file was present, it will have been modified for use on the current system, and a systemname $PRODUGX file may have been created for later (post-upgrade) use on this same system. Note that the creation of both such files is dependent on the particular service that has been applied on the already-upgraded first member system.
If a systemname $PRODS file now still exists, it has records for only components that pertain to the old release of VM. You should run PUT2PROD while logged on this system, to process these outstanding records.
Note: Until all members of this SSI cluster are upgraded to the new z/VM level, you will need to repeat the above process for every system that has not been upgraded, whenever you install service for the new level of VM.
As you upgrade the additional members of your SSI cluster, any service that you installed on the new release will be moved to the newly upgraded systems automatically — except for ICKDSF and possibly LE. To move that service into production on the systems as they are upgraded, when you complete the upgrade for each system you should:
If this file exists, you should rename it to systemname $PRODS Z and then run PUT2PROD. This will process the records that you had previously saved using the UG$PRMOD utility.
Non-SSI Volume Label and System Naming Changes
If the need arises to change the volume labels or the system name of a newly installed non-SSI z/VM system after that system has been installed (for example, to account for change over from a test installation to a production installation), please refer to:
INSTDVD Return Code (RC) 3003
Receipt of a return code value of 3003, from the INSTDVD command during an initial installation, is most likely a due to having incorrectly created the installation DVD from electronically delivered z/VM product zipped files. The unzipped product files need to be written into a folder on the DVD named CPDVD (be certain the folder name is upper case).
z/VM Licensed Product Installation Problems
When the High-Level Assembler (HLSAM) is installed on z/VM 6.3, the SERVP2P Product Parameter File (PPF) name must be specified for the VMFSETUP command that cited for use when the CMS saved system is resaved:
vmfsetup zvm cms
vmfsetup servp2p cms
System Migration - VMSES/E MIGRATE Considerations
Upon completion of traditional system migration, for which the VMSES/E MIGRATE command has been used, data associated with older-level z/VM components might persist within the VM SYSDESCT and VM SYSSUF tables on the new-level system.
The presence of such entries might then introduce various problems when service is applied to the migrated system. For example, errors could be reported by the SERVICE command, due to an attempt to receive service for an outdated component, when service for its current-level counterpart is processed. Messages associated with this situation are illustrated here, for the 620-level of the Definition and Hardware Configuration Manager for z/VM (VMHCD) and its older, 540-level counterpart):
... VMFSRV2195I SERVICE ALL envelope_name ... VMFSUI2760I VMFSUFIN processing started for product 6VMHCD20%VMHCD VMFSET2760I VMFSETUP processing started for SERVP2P VMHCD ... VMFINS2604E Product :PPF SERVP2P VMHCD :PRODID 5VMHCD40%VMHCD cannot be installed because it is not on the installation media VMFINS2760I VMFINS processing completed unsuccessfully ...
To help avoid such problem, the following utility can be obtained, and used to remove older-level entries from these files:
INSTVM Command Problems (Applies to z/VM levels prior to z/VM 620)
The problems cited here have been seen to occur if the initial installation of z/VM did not complete, either because:
While performing a second-level install of z/VM, the PUT2PROD step fails when processing the TCPIP component (with the messages shown), even though the various SFS file pool servers are logged on and active:
... DMS0VZ1153E File space is unavailable or unknown ERROR: RC99 OPENVM MOUNT /../VMBFS:VMSYS:ROOT/ / ...
CP LINK errors, associated with minidisks that have 8xxx device addresses, might be seen when one logs on the MAINT user ID:
HCPLNM102E DASD 0804 forced R/O; R/W by VMSERVS
To verify whether the INSTVM command completed successfully, the $IVM$ $FILE$ file on the MAINT 2CC disk must be reviewed. If PENDING status is present for either of these tagged sections:
then the INSTVM command did not complete successfully (or, has not been run).
To correct this problem the new level z/VM system must be IPLed (with NOAUTOLOG specified), after which the INSTVM command must be run.
Note: If for some reason, the new system has been running for any duration, with ongoing activity, or with additional changes implemented, care should be taken before the INSTVM command is invoked. It might be necessary to first save some SFS or BFS data such as data in VMSYS or VMSYSU file pools (if it was possible to store any data using these resources).