This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Reference to the BSDS for example the full image copies of the CATALOG and DIRECTORY DB2 tablespaces which are not in SYSCOPY
There are several (4 in DB2 v12) catalog and directory tablespaces for which the full image copies are not referenced in the SYSCOPY. Thus, during a DB2 cat/dir recovery (recovery exercise or other...) these FICs are searched directly in the DB2 logs, which can take a long time, depending on the volume of DB2 logs to be scanned... In order to avoid this, would it not be possible to record these FICs in the BSDS for example associated with a zparm parameter which would set the retention of this information in the BSDS? In case of a recovery in a REAL environment, it would save valuable time and reduce the downtime of DB2 Thank you for your interest in this idea.
Do not place IBM confidential, company confidential, or personal information into any field.