Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Workspace GDPS
Created by Guest
Created on Oct 28, 2026

Mechanism to remove orphaned persistent FlashCopy Relationships (RemoteCopy Services) when changing Preferred Replication Leg

If you are performing a DASD refresh/migration to new hardware using the GDPS Migration Method and have persistent FlashCopy in your environment (DB2 System Level Backup) with Incremental FlashCopy enabled. In lieu of having source application issuing FCWITHDRAW commands on the z/OS host, it would be beneficial to have the option to terminate any persistent FlashCopy on a DASD site in contained in the GEOPARM. This would prevent any orphaned FlashCopy sessions occurring that would result in failure to delete the logical volumes on the DS8000 without using the force option or removing individually, in the event you deleted a replication leg.


This could be implemented in the panel where you set the preferred RPFC leg to provide an option to remove/invalidate any background Remote Pair FlashCopy sessions for your secondary DASD (RS2 for instance) on the leg that you are going to change to be the non-preferred in a Multi Target GDPS topology.

In lieu of that an option - in the panel where you can delete pairs in the active GDPS configuration , provide the option to terminate any persistent background FlashCopy on the secondary volumes.

Yet another suggestion would be a GDPS script/command that can be issued against set of DASD in the GEOPARM (i.e RS2/RS3 , RC1/RC2) - this overlaps another idea to handle orphaned persistent FlashCopy in a zCV environment that occurred on the RCx set of Volumes.



Thanks.


Idea priority Medium