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 Not under consideration
Workspace GDPS
Created by Guest
Created on Jul 15, 2019

Support of DASD SWITCH HYPERSW RESYNC in GDPS/Metro single leg topology with MTFO=YES

In GDPS/Metro v4.1, the DASD SWITCH HYPERSW RESYNC statement no longer support with TOPOLOGY=MM2SITE and MTFO=YES.

In our site, we have a GDPS/Metro single leg environment for the production with a physically isolated LCP environment using the cascaded Global Mirror from either the PPRC primary or secondary. This setup requires the use of MTFO=YES in the MM2SITE topology.

This has introduce an additional risk to the planned hyperswap event where the alternate site disk is out of sync during the START SECONDARY. Even with the flash copy being taken before the start of PPRC resync, the DR position is aged over time until the PPRC replication is fully back in sync.

Idea priority High
  • Guest
    Reply
    |
    Nov 18, 2023
    After giving the request a comprehensive review, we have determined that we cannot include it as a candidate in an upcoming release because it won?t be pursued within our planning cycle.