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 Delivered
Created by Guest
Created on Jan 9, 2020

Support of ICF-catalogs on target vols when source of subsystem cloning is SLB RFE 83425

To use SLBs for backup/recovery it's neccessary to place the ICF-catalogs on the same volumes as DB2-data. But so far cloning-tool doesn't support handling of ICF-catalogs that reside on target-volumes during cloning-process. You should rethink if functionality could be added to fully support backup/restore. So far the ICF-catalog must be moved to another volume - that means: You have to be sure the catalog is not in use, create a new one, unload/load the contents and delete the old catalog! That's nothing any zos-systemprogramer likes to do ;-)

DB2 subsystem cloning from a DB2 BACKUP SYSTEM as source would be much simpler if handling of ICF-catalogs on target volumes would also be considered by CloningTool.

  • Guest
    Feb 20, 2020

    This enhancement was implemented in 3.2 PTF UI58442.

  • Guest
    Jan 13, 2020

    Db2 Cloning Tool has TARGET-UCATS-ON-TARGET-VOLUMES parameter in COPY command. This parameter specifies that there are target ICF catalogs that reside on the target volumes, and you want the target ICF catalogs to remain on the target volumes after the RENAME step. If Y is specified, when the RENAME step completes, the target ICF catalogs will reside on target volumes.