IBM Support

OA66660: ZDMF IS CORRUPTING VSAM FILES DURING DIVERT PROCESSING. IDCAMS EXAMINE INDICATES MISMATCH BETWEEN HI-USED RBA 6240 AND HI-ALLOC

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ZDMF is corrupting VSAM files during Divert Processing. IDCAMS
    examine indicates mismatch between HI-USED RBA 6240 and HI-ALLOC
     RBA/CI 5400.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All ZDMF 3.4.1 customers using Logical Copy  *
    *                 option.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: ZDMF is corrupting VSAM files during    *
    *                      Divert Processing. IDCAMS examine       *
    *                      indicates mismatch between HI-USED RBA  *
    *                      6240 and HI-ALLOC  RBA/CI 5400.         *
    *                                                              *
    *                       EXAMINE NAME(TEST.KSDS) ITEST DTEST    *
    *                      IDC01700I INDEXTEST BEGINS              *
    *                      IDC11709I DATA HIGH-USED RBA IS GREATER *
    *                                THAN HIGH-ALLOCATED RBA       *
    *                      IDC01702I HIGH-USED RBA/CI IS 11190     *
    *                      IDC01703I HIGH-ALLOCATED RBA/CI IS 2700 *
    *                      IDC21701I MAJOR ERRORS FOUND BY         *
    *                                INDEXTEST                     *
    *                      IDC31705I DATATEST NOT PERFORMED DUE TO *
    *                                SEVERE INDEXTEST ERRORS       *
    *                      IDC3003I FUNCTION TERMINATED.           *
    *                               CONDITION CODE IS 12           *
    *                                                              *
    *                      IDC0002I IDCAMS PROCESSING COMPLETE.    *
    *                               MAXIMUM CONDITION CODE WAS 12  *
    ****************************************************************
    Source data set is a KSDS with multiple extents on one volume.
    In addition there are at least four candidate volumes defined
    (not guaranteed space).
    
    ZDMF group is defined to use Logical Copy.
    
    During copy process the target data takes a new extent onto a
    second volume.
    
    At the end of the copy process the source data set consists of a
    data component with extents on a single volume but with
    candidate volumes. The target copy consists of a data component
    with data extents on two or more volumes and with a balance of
    candidate volumes. However, the second and any subsequent
    primary volumes do not show up in a LISTCAT of the target data
    set (renamed to the source name after the copy completes). The
    other extents of the data component can be found by using ISPF
    3.4 for the component name on other volumes in the storage
    group.
    
    The physical copy process completes correctly.
    
    The error occurs during the catalog rename process when the VVDS
    volumes records get copied in GZDRMAN. GZDRMAN attempts to
    reconcile the data component candidate volume entries between
    the source and target. In this situation the second volume of
    the source data component is identified as a candidate volume,
    whereas the second volume of the target data set is identified
    as a primary volume. In Classic ZDMF, this mismatch on extents
    does not happen and the code here swaps the volume entries to
    preserve the source definition in the renamed target. This has
    the effect of dropping a data extent from the target data set.
    

Problem conclusion

  • GZDRMAN is modified to skip candidate volume reconciliation
    during rename for data sets process by Logical Copy.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA66660

  • Reported component name

    ZDMF

  • Reported component ID

    ZDMF00001

  • Reported release

    341

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-06-24

  • Closed date

    2024-07-24

  • Last modified date

    2024-08-01

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

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

    UJ95689

Modules/Macros

  • GZDRMAN
    

Fix information

  • Fixed component name

    ZDMF

  • Fixed component ID

    ZDMF00001

Applicable component levels

  • R341 PSY UJ95689

       UP24/07/27 P F407 ¢

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":"BU048","label":"IBM Software"},"Product":{"code":"SSRLWE","label":"IBM z\/OS Data Set Mobility Facility (zDMF)"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"341","Line of Business":{"code":"LOB69","label":"Storage TPS"}}]

Document Information

Modified date:
10 November 2025