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.
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 "firstname.lastname@example.org" 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