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 Future consideration
Workspace GDPS
Created by Guest
Created on Mar 2, 2023

Report possible active CC session(s) during a planned HyperSwap

A planned HyperSwap is not allowed if there is a DFSMS Concurrent Copy (CC) session present in the GDPS environment. GDPS reports this with "HyperSwap not possible due to CC session(s) in primary or secondary disks."

The user has to use the F ANTMAIN,CCSTOR command or analyze the SMF 42(4) records to find the causing CC session. For simplification it would be very helpful if GDPS could also display the causing CC session as GDPS already knows it.

Checking at first the GDPS documentation in case of "HyperSwap not possible due to CC session(s) in primary or secondary disks." to use the required steps to find the CC session might be to long when the CC session doesn't exist anymore.

Idea priority Medium
  • Guest
    Reply
    |
    May 3, 2023

    Very helpful ...

  • Guest
    Reply
    |
    May 2, 2023

    That would be very helpful. We often have CC Sessions and it's a lot of work to find the CC which inhibit the Hyperswap.

  • Guest
    Reply
    |
    May 1, 2023

    We have not experienced issues with CC preventing planned HyperSwaps, but would use the facility if it was available when it was needed.

  • Guest
    Reply
    |
    Apr 21, 2023

    We limit the use of CC because of GDPS availability but can still get in this situation. When you do, you need all the information there is available and this would be very helpful.

  • Guest
    Reply
    |
    Apr 21, 2023

    This is very helpful for us and speeds up the process.

  • Guest
    Reply
    |
    Apr 19, 2023

    very helpful !!

  • Guest
    Reply
    |
    Apr 18, 2023

    would be helpful for us

  • Guest
    Reply
    |
    Apr 13, 2023

    Would be extremely useful. We do try to restrict CC usage to avoid problems after a UHS, but something may slip past us. At PHS not so critical, be very useful nonetheless to know what's preventing it.

  • Guest
    Reply
    |
    Apr 13, 2023

    Very reasonable request to fasten the operations.