IBM Support

OA66522: GDG DATASET PROCESSING CAN FAIL WITH MESSAGE GZD4023E WHEN CATALOG RECORD HAS EXTENSION RECORDS. ZDMF/K

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In some cases of GDGs with a large number of generations, with
    multi-volume datasets, zDMF can fail certain generation data
    sets during the divert process.  This can cause uncataloged
    versions of the generation, and the GDS is not migrated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users attempting to process GDGs that have   *
    *                 a large number of generations, with          *
    *                 multiple volumes on some generations.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message GZD4023E is issued with a       *
    *                      reason blurb of "GDS record mismatch",  *
    *                      indicating that the rename cannot be    *
    *                      completed.  It should be backed out,    *
    *                      but this fails, and the generation      *
    *                      dataset is no longer correctly          *
    *                      cataloged.                              *
    ****************************************************************
    * RECOMMENDATION: Apply the provide PTF.                       *
    ****************************************************************
    Message GZD4023E is issued with a reason blurb of "GDS record
    mismatch", indicating that the rename cannot be completed.  It
    should be backed out, but this fails, and the generation
    dataset is no longer correctly cataloged.
    The rename processing for GDGs checks for source and target GDS
    entries being both in the GDG base catalog record, or both in
    GDG extension records.  If they are not, it marks the dataset in
    error, and it should back out the dataset rename already done.
    

Problem conclusion

  • The check for having the GDG entry in the same record type is
    removed, and now processed correctly even if mis-matched.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA66522

  • Reported component name

    ZDMF

  • Reported component ID

    ZDMF00001

  • Reported release

    341

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-05-14

  • Closed date

    2024-06-26

  • Last modified date

    2024-07-01

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

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

    UJ95555

Modules/Macros

  • GZDRMAN
    

Fix information

  • Fixed component name

    ZDMF

  • Fixed component ID

    ZDMF00001

Applicable component levels

  • R341 PSY UJ95555

       UP24/06/28 P F406

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