Skip to main content

IBM Systems  >   z Systems  >   z/VM  >  

VM Installation Tips

Updated: 27 January 2017

Documentation and Planning

  • Installation Instructions for z/VM Electronic Media

    Instructions for receiving and installing electronically delivered z/VM software.

  • Preventive Service Planning (PSP) Bucket for z/VM 640 Installation

    Be sure to review the PSP Bucket for both installation information and additional program requirements. This information is stacked by date so read down through it.

  • Preventive Service Planning (PSP) Buckets Search (via the System z Technical Help Database)

    This facility provides access to PSP bucket Upgrade and Subset information (for software and hardware topics). When using this facility, be certain to place a check mark in the box for Preventive service planning, under the "Document types" heading. Then, in the "Search for" box, provide the PSP Upgrade and subset names of interest, such as:

      2817DEVICE 2817/ZVM or ZVM640 6401RSU

    Of interest:

    • To review known installation problems for a given z/VM product level, specify the applicable PSP Upgrade name (ZVMvrm) as the only search argument (where, where vrm designates a version, release and modification level). From the "Upgrade/Subset" selections that are presented, select the CP Subset, and then review the information provided under the Installation Information heading.

    • To review service recommendations, check the recommendations listed in the yynnRSU subsets listed for a given release.

Miscellaneous Information

  • 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:

Problem Information

  • 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:

    Old command: vmfsetup zvm cms
    New command: 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:

    • the INSTVM command did not complete successfully, or
    • the INSTVM command was not invoked (the INSTVM DVD command was neglected or inadvertently skipped)
    • 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:
    • :INSTPOOL / :EINSTPOOL
    • :800LINKS / :E800LINKS
    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).