This portal is to open public enhancement requests against IBM System Storage 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Had already indicated that we were handling this situation as in the next release as a defect. But will go ahead an accept the new RFE. In the next release, after removing a storage system, should the user click to remove the storage system, despite the warning message indicating that it will affect the relationships, the remove of the copy sets will act more like a remove copy set with the keep on hw option than a straight removal. Note, this means that the pairs will be removed from any GM and cg formation, but it will prevent a full copy should it occur.
I do disagree with the following statement though "Leaving relationships intact on the Storage Device when removing the storage device from CSM would prevent such exposures and be more aligned with the purpose of data replication and snapshots." CSM does already provide several ways, warning prompts etc, to prevent such an exposure. But we will make the remove keep the base relationships on the hw as this would be safer, though a customer that no longer intends to manage the pairs with CSM would need to manually clean them up if they no longer needed the relationships.