IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Created by Guest
Created on Oct 12, 2020

Add support for Cascading FlashCopy for COPY command with FASTREP(REQ) - see PTF UI172348


We take daily System Level backups (SLB) of our SAP production environments using the BACKUP SYSTEM utility.

We use Incremental FlashCopy to reduce the amount of data that needs to be physically copied to the FlashCopy target volumes and limit the pressure on the DASD subsystem.

We regularly perform Clones from our production systems into other systems, using the production FlashCopy disks as the source.

We use the COPY command with FASTREP(REQ) to guarantee that FlashCopy will be used.

Pain point:

We have to break the incremental relationship between the real production disks and their FlashCopy targets to allow us to perform the Clone. If we don't, we get the following type of error message when running the Cloning Tool COPY command:




Having to break the incremental relationship causes:

(1) operational complexity

(2) negative impact on our application workloads during the next SLB as it will force a full physical background copy.

We meet all the prerequisites to exploit Cascading FlashCopy i.e. Clone without having to end the incremental relationships in the source system (see scenario 3b in attached document).

If we issue the COPY command with FASTREP(REQ) ourselves using ADRDSSU, the command runs successfully.

If we run the Cloning Tool with FASTREP(PREF), the COPY command runs successfully and uses FlashCopy -- but we do not want to use FASTREP(PREF) as it doesn't guarantee that FlashCopy will be used.

If we run the Cloning Tool with FASTREP(REQ), we are blocked by the initial check that looks for existing relationships.

Needed by Date Apr 1, 2021
  • Guest
    Dec 9, 2020

    Thanks Jane :-)

  • Admin
    Jane Chan
    Dec 9, 2020

    Please reference PTF UI17348. @ Florence, as part of the system mechanics we had to move status to planned before we could mark it as shipped.

  • Guest
    Dec 9, 2020

    As noted by 'Guest' in the comment area, APAR PH29209 (closed) brings 'Db2 subsystem cloning supports cascading FlashCopy in its volume pairing algorithm'. Isn't that going to provide a solution for this request ?

  • Guest
    Oct 22, 2020

    This enhancement will be delivered in PH29209 APAR.