Skip to main content

IBM Systems  >   z Systems  >   z/VM  >  

VM Service News

Updated: December 15, 2016
For your awareness:

  • 12/15/2016: Updated RSU 6307 is available
    RSU 6307 is available once again. If you had ordered and received but not installed this RSU prior to December 15, 2016, please discard that shipment and reorder the RSU.

    If you had ordered and installed RSU 6307, you must verify on all systems where you had installed the RSU that the SERVICE EXEC is correct. The date of the correct SERVICE EXEC, found on the MAINT630 5E5 and 5E6 disks, should be 6/20/2014 (June 20, 2014). If you have a copy that is dated 5/18/2016 (May 18, 2016) it must be replaced with the correct version.

    Follow the steps below to verify the date of the SERVICE EXEC and update any incorrect copies with the correct version:

    1. Log on to MAINT630
    2. If you installed VM on minidisks:
      If you installed VM to the shared file system (SFS):
    3. ACCESS 5E5 O
      This will display a list of the SERVICE EXECs on you system. If the date on the file on the B (5E6) disk and/or the O (5E5) disk is not 6/20/2014, you should perform steps 5 and 6. If the date is correct on these two disks no further action is necessary.
      where B is the filemode of the 5E5 disk
      where O is the filemode of the 5E5 disk
      where J is the filemode of the Delta disk (5D2 or VMPSFS:MAINT630.VMSES.DELTAPROD)
      where J is the filemode of the Delta disk (5D2 or VMPSFS:MAINT630.VMSES.DELTAPROD)

  • z/VM storage configuration after applying VM65586 / UM34552 - After applying VM65586 / UM34552, the storage configuration you will see after an IPL may be different than it was before the IPL. For more details, refer to Informational APAR II14812

  • Required Service for z/VM 6.3 and z/VM 6.2 to run on IBM z13 Driver 27, LinuxONE Emperor, IBM z13s and LinuxONE Rockhopper. (February 16, 2016)

  • Required service for z/VM 6.3.0 to run Security Enhancements (September 2015)

  • HCPRLE1944I Architecture incompatibility failure on VMRELOCATE command (August 2015)

    When relocating a z/VM guest with the VMRELOCATE command, in some cases the relocation can fail with message "HCPRLE1944I Architecture incompatibility." This section explains why this can occur, and the steps that must be performed jointly by the customer and z/VM service personnel to handle the problem.

    z/VM issues message HCPRLE1944I when it detects that the architecture of the relocation destination SSI member is not compatible with the set of machine facilities available to the guest being relocated. z/VM cannot allow this relocation to occur, because if the guest being relocated was previously informed of and has begun using an architecture feature that is not available on the destination member, the guest could encounter problems and possibly abend after relocation completes. The rejection of a relocation in this case is a normal and expected z/VM function.

    A shortcoming of z/VM in this instance is that detailed error messages are not issued explaining what the architecture incompatibilities are. In addition, application of z/VM service to individual SSI members can inadvertently introduce architecture incompatibilities, or cause HCPRLE1944I to be issued unnecessarily. Because of this, customers do not have enough information to know what action should be taken to deal with this situation. As a result, customers must do the following:

    1. Open a Service Request and describe the problem.
    2. Download RELODOM EXEC from the VM Downloads page . Optionally, you can request that Level 2 support send it to you. This EXEC gathers architecture information from z/VM control blocks, and it must be run from a class C or E user on both the relocation source and destination members.
    3. Send the EXEC output to z/VM Level 2 support.

    z/VM Level 2 support will analyze the data as quickly as possible and will provide advice based on this analysis. Level 2 support may suggest actions such as using the FORCE ARCHITECTURE option on the VMRELOCATE command, adjusting the service levels on the SSI members, adjusting architecture facilities, or other remedies.

    An example of a case in which z/VM customers have encountered this type of problem is with APAR VM65417 - GUEST SUPPORT OF ZEDC EXPRESS AND 10GBE ROCE FEATURES. This APAR was introduced on RSU 1501. A typical scenario for this problem follows:

    The customer is running a 2-member SSI cluster with members named VMMEM1 and VMMEM2. Each member has the same CP service level installed, which does not include VM65417. In preparation for applying VM65417 to VMMEM1, guest VMPRODA is successfully relocated to VMMEM2. VM65417 is applied to VMMEM1 and then reIPLed. Because base code in z/VM 6.3.0 and VM65417 is not coded properly, the relocation of VMPRODA back to VMMEM1 is prohibited and the HCPRLE1944 message is issued. In this case, the customer is instructed by Level 2 support to run RELODOM EXEC and send the data that is collected to Level 2 support. Level 2 support analyzes the data and determines that the only existing architecture incompatibilities are due to the base release z/VM 6.3.0 and VM65417 code problem. Level 2 support then instructs the customer to use the FORCE ARCHITECTURE option to safely and successfully relocate VMPRODA.

  • VMHCD component needs additional space when installing z/VM HCM service to support IBM z13
    The service required by the VMHCD component to support the IBM z13 for z/VM 6.2 and z/VM 6.3 (APARs VM65489 (HCD) and VM64437 (HCM)) or for toleration of the IBM z13 for z/VM 5.4 (APARs VM65658 (HCD) and VM64659 (HCM)) needs additional space on the service disks for the HCM service. Note: The HCM service is only required if you are using z/VM HCM which is the graphical user interface to z/VM HCD. This article explains how much space is needed for the service disks when installing the HCM APAR.

  • Required Service for z/VM 6.3 and z/VM 6.2 to run on IBM z13. (January 14, 2015)

  • z/VM and Heartbleed
    We have had several people ask us if z/VM is affected at all by the Heartbleed bug that has been discussed recently. We can state with certainty that z/VM does NOT have any problem related to the Heartbleed bug. The z/VM SSL support shipped with the TCP/IP component is not based on openssl and does not have the Heartbleed problem. The other z/VM components do not have any capability built into them. They rely on the SSL shipped with TCP/IP. This is true for all supported releases of the SSL server code in all supported z/VM releases (z/VM 5.4, 6.2. and 6.3).

    There is one caveat to the above statement. If you are running z/VM 6.3 and running the xCAT server, there is an openssl component of that server. We have verified that the openssl component does not contain the Heartbleed bug.

  • A change was made to the HIPER APAR classification. (March 2013/May 2007)
    HIPER APARs used to be defined as "Highly Pervasive". The HIPER designation is now given to an APAR that addresses the following type problems:
    • System or subsystem outages
    • The inability to recover from failure
    • Loss of major program function
    • Recursive failures
    • Severe performance failures where it's extremely difficult to proceed without a bypass or circumvention and ultimately an APAR fix solution.
    The RSU content will remain the same. The mechanism z/VM is using to include an APAR on the RSU is HIPER and PERVASIVE which is in line with the old HIPER definition. This will not effect RSU distribution dates.

    APAR's with the HIPER designation are tracked by many z/VM users. This new definition enables z/VM customers to be informed about serious problems that may effect their environment. APARs flagged HIPER and PERVASIVE should appear in the PSP bucket. You can then review them and see which ones you need to apply.

  • Required Service for z/VM 6.3, z/VM 6.2, z/VM V6.1 and z/VM V5.4 to run on IBM zEnterprise EC12 and BC12 Systems. (August 2013)

  • Refer to z/VM Installation News or z/VM Installation Tips for z/VM installation information or reported problems.

  • Here is important service information for customers running with the IBM zEnterprise Unified Resource Manager. (updated 02-2012)

  • Customers who are using HyperSwap and are exploiting FlashCopy from PPRC devices when the PPRC pairs are suspended can run into a potential data loss problem. Review the following two items for more information on this situation to see if this affects your system or not.

  • Here is Important Information if you are running z/VM 6.1 SMAPI and do not use Unified Resource Manager and have stacked 6105RSU (CMS LEVEL 1101) (September 2011)
  • Required Service for z/VM V6.1 and z/VM V5.4 to run on IBM zEnterprise System (z114). (July 2011)
  • New Red Alert for those who run Linux on z/VM V6.1 and/or V5.4:
    APAR VM64862 is in error. View details at z/VM Red Alert. (April 2011)
  • New Red Alert pertaining to z/VM V6.1 and V5.4: SSL Server Performance and Scalability Enhancements - Packaging Updates (Aug. 2010)
  • Required Service for z/VM V6.1 and z/VM V5.4 to run on IBM zEnterprise System. (07-2010)
  • New Red Alert pertaining to all z/VM customers running guest coupling support when they have both an IBM System z10 and the PTF for APAR VM64793 (June 2010)
  • Required Service for z/VM V6.1, z/VM V5.4 and V5.3 to support Crypto Express3 and to use 3590 and 3592 Tapes with Ficon Express8, Express4, and Express2. (11-2009)
  • New Red Alert pertaining to z/VM V6.1, V5.4, V5.3 -- all users running OSA-Express3 devices with microcode level 7.31.0 and beyond who have a z/VM TCP/IP stack configuration that includes a VIPA interface. (Oct. 2009)
  • New z/VM V5 R4 Red Alert for any VM user with a CPOWNED pack in TPF mode (April 2009)
  • Updated service levels for HCD (05-2009)
  • Updated service levels for HCM (09-2009)
  • Updated Informational Files for z/VM V5.4 DVD Install
  • Required Service for z/VM V5.3 and V5.2 in order to run on the new System z10   (10-2008)
  • New z/VM Red Alert page created for Critical Issues (Nov. 2007)
  • View 2008 plans for z/VM V5.1 , z/VM V5.2 and z/VM V5.3 RSU. (04-2008)

  • z/VM V5.2 PTF UM31784 application information  (12-2006)

    The PTF, UM31784, is a collection of z/VM 5.2.0 new function APARs. IT IS NOT AN RSU but a large cumulative CORrective service deliverable. You install this PTF by using the SERVICE command or the VMFREC command. The VMFINS command will not work against this PTF.

  • Daylight Saving Time 2007 Changes (DST2007) (11-2006)
    A provision of the U.S. Government's Energy Policy Act of 2005, extends Daylight Saving Time (DST) by four weeks, beginning in 2007. Starting in March 2007, daylight time in the United States will begin on the second Sunday in March and end on the first Sunday in November. Read the document describing how the changes to U.S. daylight saving time affect z/VM
  • Required Service for z/VM 5.2.0   (04-2006)
    • Do not IPL z/VM V5.2 first level in an LPAR until the following MCL levels for z890 and z990 machines have been applied and activated.
      MCL J13484.112
      MCL J13486.106
      MCL J13471.007
    • In order to run LINUX KERNEL 2.6.16 in a virtual machine, the following MCL levels must be applied:
      J13484.137 for z890 and z990
      J99673.083 for System z9

      Since Linux kernel 2.6.16, the Linux on zSeries QDIO-module exploits the new z/VM 5.2 high performance method to transmit data for dedicated FCP, OSA and HiperSockets devices called QDIO Enhanced Buffer State Management (QEBSM) on z890, z990, and z9-109.
  • Potential Support Element problem on z/VM V5.2 with APAR VM63815

    NOTE: APAR VM63897 is now available (January 5,2006) and prevents the problems associated with APAR VM63815 and the support element/HMC.

    APAR VM63815 may cause Support Element (SE) to run out of memory and re-boot. The problem has NOT been seen on the new 2094 (z9-109) processors. This does not cause a problem with the systems running in the LPAR's. This only effects the SE and Hardware Maintenance Console (HMC). This maybe noticed by slow-downs and hangs on the HMC. Likewise, the same symptoms might be noticed on the SE as well, followed by it re-booting. Once SE has re-booted, HMC and SE return to working like normal, however the problem process will start over again.

    SE development has been made aware of this problem and its severity and is actively working on a solution with z/VM development.

    APAR VM63815 was shipped on latest RSU supplied with z/VM V5.2. The PTF is not on an RSU yet for other releases. The PTF numbers for each release are:

    R520 PTF UM31545  0501RSU
    R510 PTF UM31544  Not on RSU
    R440 PTF UM31543  Not on RSU
    The current work around is to apply VM63897, or if this is not an option, back off the PTF, for this APAR, using the VMFREM command, as defined at: (remove PTF for VM63815)
  • Dates and APAR Information for Recent Enhancements for z/VM in support of Oct. 2004 and Jan. 2005 hardware announcements.
  • Hardware requirements installing z/VM V5.1 from DVD
  • Updated service for z/VM HCM and HCD 01-2006
  • z990 Adapter Interrupt Performance:
    Check for appropriate service levels if you plan to put z990 Adapter Interrupt technology into production. (Jan. 26, 2004)
  • Extended End of Service dates for z/VM V4.3 and for z/VM 4.4 with z/VM V4 Software Support Lifecycle Extensions (Aug. 12, 2003)
  • z/VM V3.1, V4.2, and V4.3 on the new IBM eServer zSeries 990 server
    Refer to the z/VM subset of the 2084DEVICE Preventative Service Planning (PSP) bucket prior to installing the z990 server. (May 13, 2003)
  • Hardware requirements when operating the Integrated 3270 Console on pre-z990 servers with z/VM V4.4 Hardware Management Console Version 1.8.0 or later is required if....(read more)
  • IBM Shopz
    Shopz is an IBM productivity tool for planning and ordering zSeries software products and service. Now you can order a variety of tailored software packages for the z/OS, z/OS.e, OS/390, z/VM, VM/ESA and VSE/ESA environments. Shopz also lets you review your software licenses in these environments.
    Note: Not all Shopz features are supported in all countries.
  • VM support is available (01-25-2002) for the IBM TotalStorageTM Enterprise Storage Server new configuration options. (See announcement letter 101-341.)

    3390 model 9 DASD configured up to 32,760 cylinders
    Supported on z/VM 3.1.0 and subsequent releases. The following VM PTFs are required:

    • - APAR VM62936 for CMS R310 thru R420. PTF numbers are UM30246(310), UM30247(410), and UM30248(420).
    • - APAR VM62937 for GCS R310. PTF number is UM30249.
    • - APAR VM62907 for DIRMAINT R150 and R410. PTF numbers are UV60704(150) and UV60703(410).
    • - APAR VM63004 for DFSMS F221. PTF number is UM30242.
    • - APAR VM62767 if CSE XLINK minidisk links are used on the R310 CP component of z/VM. This is only necessary if XLINK is used. PTF number is UM29928.

    The following microcode upgrade is needed:
    • IBM TotalStorage microcode upgrade Version or later, AEC# SC11212, Part# 13461131

    Control-Unit-Initiated Reconfiguration (CUIR)

    • Supported on VM/ESA 2.3.0, or later and z/VM 3.1.0, or later.
      No VM PTFs are required for CUIR support.
  • Ordering specific VM PTFs using the INTERNET

    From the --> IBM Support Portal for z/VM, you can order PTFs for a VM system. It may not be as robust as ordering through the support center but if you have been keeping up with the latest service and need a specific PTF it is a good, and usually quick, way to get it. Ordering fixes from that site requires an IBM common registration userid.

  • All VM customers applying APARs that have a memo file that is part of the APAR, can find the memo information at the bottom of the prodid MEMO that comes on the COR service tape. If the order was electronic, then the prodid MEMO can be found in the VLSTnnnn file of the electronic order. An example of such an APAR is VM62480 (click to go to memo).