IBM Support

VM66887: PEVM66877 Z/VM 7.4 CP: FIX PACK - FEATURE 03 FIX 01

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This is Feature Pack 03 Fix Pack 01 for z/VM 7.4. It contains
    fixes for the following problems:
    
    1. ABENDHTT001 HCPVIT+374 purging tracks from MDCACHE
    2. Paths grouped for offline secondary PPRC devices
    3. CPSYNTAX improperly handles entries with leading zero slots
    4. FCP cannot be detached after adding a path with an incorrect
    LUN
    5. FLASHCOPY VDEV causes Metro Mirror suspend
    6. Console override may fail when using SYSG in IPLPARMS
    7. ABENDFRE001 obtaining storage for message buffer length < 0
    8. Error code =106 when re-adding a path to an EDEVICE
    9. PEVM66877 Dev init fails with conflict error 2nd level
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All z/VM users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    ABENDHTT001 HCPVIT+374 purging tracks from MDCACHE
    ----------------------------------------------------------------
    An HTT001 abend was received due to a copy SUC IORBK having a
    non-zero value in the MDC purge block field (IORPURGE). A copy
    SUC IORBK is a copy of the original IORBK used to present the
    unsolicited summary unit check.
    
    Fix ensures that the IORPURGE field will be cleared for copy
    IORBKs created for SUC processing.
    
    
    
    Paths grouped for offline secondary PPRC devices
    ----------------------------------------------------------------
    CHPID error detection causes remaining paths to an offline PPRC
    device to end up grouped. This causes PPRC to not be able to
    resync following a suspend.
    
    This error recovery will be updated to not refresh and regroup
    the paths for offline devices.
    
    
    
    CPSYNTAX improperly handles entries with leading zero
    ----------------------------------------------------------------
    The CPSYNTAX EXEC uses the parsed slot token directly as a REXX
    stem tail. When the slot value includes leading zeros (for
    example "01" through "09"), variables such as global.xlinkin.01
    are created. Later validation loops iterate numerically (1
    through n), so global.xlinkin.01 is never referenced. This
    causes INCLUDE entries for slots 01 through 09 to be lost and
    can result in HCP6827E being issued even though the system name
    was correctly specified in the configuration file for statements
    like XLINK SYSTEM INCLUDE. This also affects the CP_OWNED syntax
    checking.
    
    
    
    FCP cannot be detached after adding a path with an incorrect LUN
    ----------------------------------------------------------------
    When an EDEV is online, adding paths using the wrong LUN will
    cause the FCP associated with that path to remain attached to
    the system despite the path already being deleted.
    
    
    
    FLASHCOPY VDEV causes Metro Mirror suspend
    ----------------------------------------------------------------
    Addition of the ALLOCATE and NOALLOCATE options for the
    FLASHCOPY VDEV command. This gives users control over
    pre-allocating target Extent Space Efficient volumes. Dictate
    the activation of certain compression related Flashcopy
    options based on device features supported and other
    FLASHCOPY command operands. Also add compression information
    to the RDEV for dump and debug when dealing with compression
    volumes.
    
    
    Console Override may Fail when using SYSG in IPLPARMS
    ----------------------------------------------------------------
    When IPLPARMS includes multiple CON/CONS parameters, CP is
    supposed to ignore all previous occurrences. However, earlier
    specifications of SYSG may still take precedence resulting in a
    HCP1010W. This fix resets the extraneous flags
    when processing each CONS parameter and only honors the final
    one.
    
    
    
    ABENDFRE001 obtaining storage for message buffer length < 0
    ----------------------------------------------------------------
    ABENDFRE001 trying to obtain storage for asynchronous message
    to present to a tape device. Buffer length used was
    negative. This negative number caused the storage request to
    look like a very large positive number, causing the abend.
    
    
    
    Error code =106 when re-adding a path to an EDEVICE
    ----------------------------------------------------------------
    During issues with path recovery like FCPs being put in a
    checkstopped state, a 106 error may be encountered when
    attempting to re-add paths through certain FCPs. The FCP device
    gets stuck in an active state despite being detached from the
    user, and a system re-IPL is required to clear the FCP device so
    that it can be used again for path definition. This is the
    result of an error in the code that failed to properly close the
    FCP device during the gathering of monitor data for CHPIDs and
    FCP devices.
    
    This fix ensures that FCP devices are closed properly during
    recovery events so that the 106 error will no longer occur.
    
    
    PEVM66877 Dev init fails with conflict error 2nd level
    ----------------------------------------------------------------
    A guest z/VM system experienced device initialization errors
    for virtual devices during system initialization failing with
    the following message:
         HCPIIO6284I Device nnnn cannot be varied online due to
         conflicting device classification information.
    Depending on the failing devices, this error could cause the
    guest z/VM system to fail IPL.
    
    Device initialization includes a check to determine if the
    device is associated with any type of OSA channel path. If it
    is, it will verify that the device class and device type
    in the RDEV are valid for an OSA device. If they are not, then
    device initialization fails with the above conflict message.
    This OSA channel path check is not valid for z/VM systems
    running as a guest.
    

Problem conclusion

  • ABENDHTT001 HCPVIT+374 purging tracks from MDCACHE
    ----------------------------------------------------------------
    Fix ensures that the IORPURGE field will be cleared for
    copy IORBKs created for SUC processing.
    
    
    
    Paths grouped for offline secondary PPRC devices
    ----------------------------------------------------------------
    Call to HCPDPMNL from HCPIFIIN should be skipped for offline
    devices to prevent their paths from being grouped while they are
    offline.
    
    
    
    CPSYNTAX improperly handles entries with leading zero
    ----------------------------------------------------------------
    A normalize slot helper function was added that strips leading
    0s from slot numbers while preserving "0" when the value is
    zero. This ensures Slot 01-Slot 09 are stored as 1-9 and
    correctly processed by CPSYNTAX. The same issue was also present
    in the CP OWNED statement processing. That was fixed with the
    same normalize logic as well. With these changes, valid entries
    are no longer skipped and HCP6827E is no longer issued
    erroneously.
    
    
    
    FCP cannot be detached after adding a path with an incorrect LUN
    ----------------------------------------------------------------
    To address the problem of FCP's remaining attached to the
    system, the path count was decremented and the FCP was detached
    when the count reached 0. Buffer storage was moved as
    needed. Furthermore, code was added to bypass this process when
    the EDEV was offline, ensuring the FCP will detach from the
    system in all use cases.
    
    
    
    FLASHCOPY VDEV causes Metro Mirror suspend
    ----------------------------------------------------------------
    ALLOCATE and NOALLOCATE operands were added to the FLASHCOPY
    vdev command. This prevents ESE DASD pre-allocation if
    NOALLOCATE is specified. ALLOCATE will turn on the pre-allocate
    flag, which is ignored by DASD that are not ESE. The conserve
    tracks flag is now turned on when the pre-allocate flag is on
    and the RDEV block flag corresponding to the device feature is
    on. Compression information is also now available in the RDEV
    for future debug and dumps. Control unit and device
    initialization code was modified to move the conserve tracks
    feature and the compression indicators into the RDEV from their
    associated IO responses.
    
    
    
    
    Console Override may Fail when using SYSG in IPLPARMS
    ----------------------------------------------------------------
    Logic was added to IPLPARMS CONS processing to ensure only one
    override setting is in place after each statement is
    processed. Only the last statement's settings will remain in
    place once processing is complete.
    
    
    
    
    ABENDFRE001 obtaining storage for message buffer length < 0
    ----------------------------------------------------------------
    HCPSVIAP (Asynchronous Message Reflection Routine)
    was modified to change its local variable for the message size
    from a fixed(15) signed variable to a fixed(16) unsigned
    variable. This will prevent the possibility of a message
    size turning negative and appearing as an illegally large
    value for a storage request that would cause an ABENDFRE001.
    
    
    
    Error code =106 when re-adding a path to an EDEVICE
    ----------------------------------------------------------------
    106 error codes may be encountered when re-adding a path to an
    EDEVICE after certain recovery events like FCPs being
    checkstopped. The 106 error code indicates that the FCP device
    is still in an active state despite the FCP having been detached
    from the user, and it prevents any new paths from being added
    using that FCP device until a system re-IPL can be done to clear
    the FCP device state. This was found to be an error due to a bug
    in the code where the FCP device is not properly closed during
    certain failures encountered when gathering monitor data for
    CHPID and FCP devices, thus causing further issues when the FCP
    device is forcefully detached from the user during certain
    recovery situations. The fix ensures that proper cleanup is done
    during monitor data requests so that the FCP device will be
    closed properly and no longer cause 106 errors when re-adding a
    path to the EDEVICE through the FCP device.
    
    
    
    PEVM66877 Dev init fails with conflict error 2nd level
    ----------------------------------------------------------------
    PEVM66877 Device initialization code was modified to not perform
    the OSA channel path check for devices when the system IPLing
    is a guest z/VM system. This will prevent some virtual devices
    from failing device initialization with a conflict error.
    

Temporary fix

Comments

  • ×**** PE26/01/14 FIX IN ERROR. SEE APAR VM66912  FOR DESCRIPTION
    ×**** PE26/01/14 FIX IN ERROR. SEE APAR VM66912  FOR DESCRIPTION
    

APAR Information

  • APAR number

    VM66887

  • Reported component name

    VM CP CP

  • Reported component ID

    568411202

  • Reported release

    740

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-09-26

  • Closed date

    2025-11-21

  • Last modified date

    2026-03-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UM90571

Modules/Macros

  • CPSYNTAX HCPARM   HCPCPE   HCPICU   HCPIFI   HCPNFC   HCPQPA
    HCPRDEV  HCPRDI   HCPSDU   HCPSDV   HCPSVI   HCPSZB   HCPSZP
    VDEV     7VMCPR40
    

Publications Referenced
SC24626874    

Fix information

  • Fixed component name

    VM CP CP

  • Fixed component ID

    568411202

Applicable component levels

  • R740 PSY UM90571

       UP25/11/25 P 7404 ¢

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SG27M","label":"APARs - z\/VM Environment"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"740","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
24 March 2026