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,
Post an idea
Upvote ideas that matter most to you
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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.