Skip to Main Content
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 Not under consideration
Created by Guest
Created on May 23, 2022

Implement Inline Image Copies for COPY YES Indexes during Reorg utility operations

There appears to be expected functionality missing within DB2 Reorg Index (and Tablespace) utility operations to allow "normal" Image Copies to be taken inline for Indexes that have been defined as COPY YES similar to the inline Image Copies that can be taken for Tablespaces being reorged. Instead the COPY YES Indexes are placed in Informational Copy (ICOPY) status to show they are no longer recoverable. This means that despite the Indexes being defined with COPY YES that they are unrecoverable and would need to be rebuilt in a recovery scenario until an Image Copy is taken. (IBM have implemented Flashcopy Image Copy support with Reorg Index but not the ability to take "normal" inline Image Copies) This scenario could lead to extended recovery times for customers who were expecting large Indexes to be recovered rather than rebuilt. Instead customers would need to be aware to take a manual Image copy immediately after a Reorg Index or Reorg Tablespace operation that impacted COPY YES Indexes and put them in ICOPY status when this could theoretically be performed as part of the reorg process. Are IBM able to add this additional functionality to the reorg utility ?
  • Admin
    Janet Figone
    Jun 21, 2022

    Dear Nat West group,

    Development agrees that taking inline copies of COPY YES indexes as part of utility executions to avoid leaving indexes in ICOPY is desirable and is part of our longer term strategy. However, the ICOPY state does not impact applications and the indexes can be rebuilt if necessary. Also, automation can be put in place to create new image copies for ICOPY indexes. On this basis there are other utility items that have higher priority at this time and so this item is not currently under consideration.

    We appreciate your input and hope that you will continue to submit enhancement suggestions for improvements as customer feedback is a key component to shaping the future direction of our products.


    The Db2 for z/OS and Tools team