IBM Support

OA66750: RENAME FAILS IF SOURCE AND TARGET FILE ARE ON THE SAME VOLUME WITH GZD4030E ZDMF/K

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using Logical Copy, and the target file is allocated on
    the same volume as the source file, the rename process at the
    end of Divert processing fails with message GZD4030E. Also,
    both source and target are inaccessible due to being
    incorrectly cataloged.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the Logical Copy feature.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: When target datasets for a zDMF         *
    *                      migration are allocated on the same     *
    *                      volume as the source, the Divert        *
    *                      rename process fails.                   *
    ****************************************************************
    * RECOMMENDATION: Apply provided PTF when available.           *
    ****************************************************************
    When users want to perform a migration of datasets, but keep
    them in the same STORGRP, failures occur because the Divert
    rename logic could not swap dataset names when they were on
    the same volume.  A related issue is that target dataset names
    can be either the new, processed dataset, or the old source
    dataset, and there is no obvious way to determine if the
    rename has been done when problems occur.
    

Problem conclusion

  • The Divert rename process has been updated to this sequence:
    1. Create the target dataset with a last node of .T00000
    2. In Divert, the source dataset is renamed to the same as the
       target, except last node is .S00000
    3. Finally, the target dataset is renamed to the source dataset
       name.
    This avoids an attempt to have two datasets with the same name
    on the same volume (which would fail).
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA66750

  • 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-07-18

  • Closed date

    2025-07-03

  • Last modified date

    2025-08-02

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

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

    UJ97528

Modules/Macros

  • GZDACT0  GZDRENV  GZDRMAN
    

Fix information

  • Fixed component name

    ZDMF

  • Fixed component ID

    ZDMF00001

Applicable component levels

  • R341 PSY UJ97528

       UP25/07/11 P F507

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