IBM Data and AI Ideas Portal for Customers
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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Hi Janet, thank you for your reply and suggestion.
I was hoping that there would be a way to add LASTUSED column to the SYSIBM.SYSTABLES catalog table with details for all the various types and the users could run a simple query.
However, if the only way for IBM to introduce new feature is by creating a new trace record for object dependencies, we could create a process inhouse which collects the view access information from the trace and store it in a Db2 table to be used in conjunction with the SYSPACKAGE.LASTUSED column in determining if a view is being used or not.
Kind Regards,
Laszlo
Hello Laszlo, Our Db2 for z/OS development team has continued to review this idea and has provided the following feedback and question for you:
We are thinking that for static SQL, you can query the view dependency in SYSPACKDEP and monitor usage via SYSPACKAGE.LASTUSED. For dynamic SQL and static SQL which needs to go through incremental bind, we can consider writing a new trace record for object dependencies. You'd need to monitor the new trace and SYSPACKAGE.LASTUSED over time while exposing all applications, before confidently dropping the view. Is this an acceptable solution?
We will await your response.
Sincerely,
The Db2 for z/OS Team
We have thousands of views with a similar situation. we cannot drop the views since the app area is unsure if the view is needed or not. A way to track last used on a view, synonym or alias would be an advantage in system cleanup