Skip to Main Content
IBM System Storage Ideas Portal

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Mar 27, 2020

z/OS HyperSwap and Concurrent Copy

After a HyperSwap, the command "Start H2->H1" (Start H1->H2 respectively) will fail if there a active Concurrent Copy Sessions on secondaries (former primaries). CSM will show error IWNR2108E RC 0F13.

We know IBM recommends to eliminate any Concurrent Copy usage in a HyperSwap configuration. The recommendation relies on the disadvantage of z/OS HyperSwap with CSM. CSM can not terminate Concurrent Copy Sessions.

We would like to have a soulution like GDPS do.
A planned HyperSwap should be prevented if there are active CC Sessions found. An unplanned HyperSwap should be possible of course.
The Start command (like START SECONDARY in GDPS) should terminate active CC Sessions so nothing will prevent an establish PPRC pair relationship after a HyperSwap.

Idea priority Medium
  • Guest
    Mar 30, 2020

    CSM can look into possible removing the CC's after the swap however a planned swap could be issue from the z/OS side as well as CSM side. I would suggest opening a corresponding request to the HyperSwap team on z/OS to prevent a planned swap if Concurrent Copy exists