IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

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

https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 9 2020
  • Delivered
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    20 Feb 09:02am

    This enhancement was implemented in 3.2 PTF UI58442.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    13 Jan 11:13am

    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.

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions