Skip to main content

IBM Systems  >   z Systems  >   z/VM  >  

z/VM Service: Red Alerts

This page is intended to provide information about potential high-impact items and in some cases prior to the opening of an APAR. Note that when a release level reaches the end of service, we intend to remove the item from the list.

Date Description
13 Dec 2017 Avoid IPL Failures - Reminder to update the Stand Alone Program Loader (SAPL) for z14
10 July 2017 APAR VM66026 is in error.
Apply PTF for APAR VM66036.
17 Nov 2014 VM65544 is now available
10 Nov 2014 VM65544 is required prior to DS8K R7.4
13 Oct 2014 VM65619 required to avoid storage corruption for guests greater than 4G


  • Dec 13, 2017 (Updated 12/22/17 for clarity)

    Avoid IPL Failures - Reminder to update the Stand Alone Program Loader (SAPL) for z14

    If you are considering upgrading your hardware to a z14, you must read, understand, and comply with all of the text included in these APARs to avoid z/VM IPL problems:

    • VM65942 - z/VM support for z14 with driver D/T3906
    • VM65856 - ESA/390 Removal Support for z/VM V630


    All z/VM Users planning to migrate to z14


    If you do not upgrade SAPL as instructed, you will not be able to IPL z/VM on the z14. Customers are urged to upgrade SAPL as instructed immediately because it is very difficult to do this once the z14 is installed.


    These APARs are included in the base of z/VM 6.4.0, but must be applied if you are running z/VM 6.3.0. However, for both 6.3.0 and 6.4.0 releases, this is a reminder that there are MANUAL STEPS that MUST be performed in order for you to IPL z/VM on a z14. In particular, the steps for upgrading SAPL are critical to the operation of your system and must not be skipped. These steps are referenced in the APARs above, and for 6.4.0 users in the "Post upgrade installation" section of the 6.4.0 Installation Guide manual. For 6.4.0 users, here is the step from the 6.4.0 Installation Guide:

    "Changes made to the Stand Alone Program Loader in z/VM 6.4.0 require that the SALIPL record be rewritten to the IPL volume. Rewrite your SALIPL record using the z/VM 6.4.0 level of the SALIPL MODULE. See Chapter 2, "Using the Stand-Alone Program Loader", in z/VM System Operation 6.4 for instructions on rewriting the SALIPL record."

    For 6.3.0 users, VM65942 says that you must install SAPL with the updated SALIPL provided by the PTF for APAR VM65856. For instructions on installing SAPL, refer to Chapter 2 of the z/VM System Operation 6.3 manual.

  • July 10, 2017

    APAR VM66026 is in error. See problem resolution.



    All users of HyperPAV and zHPF


    It may cause serious problems if you are using system-attached HyperPAV / PAV alias devices. This APAR closed on June 7, 2017 and is NOT on an RSU. "VM66036 PEVM66026 ABENDPRG006 ON SYSTEM ATTACHED ALIAS I/O" has been opened to fix this, and the fix is in our internal test phase.

    These alias devices can be attached to the system with either the SYSTEM_ALIAS configuration statement in SYSTEM CONFIG, or the CP ATTACH command.


    Apply PTF for APAR VM66036

2014: A PDF version of 2014 z/VM Red Alerts can be found here.

  • November 10, 2014

    APAR VM65544 is now available.

    WARNING: APAR VM65544 must be applied prior to DS8K R7.4 to avoid outages


    All users of z/VM planning to move to the DS8K R7.4 level


    Installations using z/VM who are planning to move to the DS8K R7.4 level MUST apply the PTF for z/VM APAR VM65544 prior to upgrading their DS8K. Failure to apply this APAR may result in unplanned z/VM outages when any PPRC operation is initiated, whether new R7.4PPRC function is exploited or not. PTFs will be available for supported z/VM releases, 5.4, 6.2, and 6.3. DS8K R7.4 contains support for Multi-Target PPRC.


    Apply APAR VM65544.

  • October 14, 2014

    APAR VM65538 is in error

    For any guests with storage greater than 4G, using minidisk cache (MDC) or Read Track Data CCWs may result in a guest storage overlay.


    All users of z/VM 6.3 with APAR VM65538 running guests > 4G (eg. Linux).


    VM65538 incorrectly clears the high half of a register containing an IDAW data address. This causes addresses greater than 4G to become corrupted. The usual result is not being able to boot Linux. which uses the Read Track Data CCW with an IDAW address >4G when the guest storage is 4G or greater.

    The use of MDC may also result in data being stored at the wrong address for any guest with storage >4G. MDC must remain disabled for the entire life of the guest.


    There are two options to avoid the problem.

    1. Apply APAR VM65619.

    2. Restrict guests to less than 4G.

Do you want to be notified when this page changes? Click on Notify Me in the left-hand column and complete the form to receive a notice when this page changes.