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
Provide Db2 history of installs/updates including date
For auditing and compliance purposes, Db2 needs to easily make the following information available: - Database Version, Release, ModPack, FixPack (including security special builds) - Database Date/Time of the creation and subsequent updates - Database Build Level - Associated Instance Version, Release, Mod Pack, Fix Pack - Associated Instance Date/Time of install/update - Associated instance Build Level
The above information is preferred to be accessible in a single query to a system catalog table to support reporting purposes across all Db2 databases in the enterprise. Presently, some of the information is available, but it requires multiple queries and does not provide all the needed data. For example, sysibm.sysversions provides valuable history about the database and includes a timestamp, but the timestamp does not appear to represent when the latest update was installed and being a sysibm table is technically not for users and there's no documentation.
ENV_INST_INFO provides instance information, but it does not include a date when the instance was updated and lacks historical information.
A preferred solution would be to formalize sysibm.sysversions to syscat.sysversions and extend the output to include logging a date/time of every database update as well as providing the same information about the associated instance.
Do not place IBM confidential, company confidential, or personal information into any field.