This is an IBM Automation portal for Cloud Platform products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
The request is for the "last access time" of a DO object to be the last time it was winked in to a view. Right now, the last access time is reported as = original creation time (and not stored at all in the VOB). Dumping the DO will tell you the FIRST winkin date/time, which is of minimal use when trying to manage DO storage pool size.
Also, right now the %d format option appears to print the date of the original DP creation. There will need to be a way to report on the last winkin time for recording it to be of use.
SF case: TS008770225. Escalation: CHCLS00155182.
Currently, the "last access" in "lsdo -l" output never changes. It is always the same with the DO creation date. As per CHCLS00155182, customer wants to update it to be "Last accessed time of a DO when it is winked in".
Customer's VOB has about 400GB ~ 500GB DO data. Using the Scrubber to delete DO which has 0 reference count can only reduce about 10% of them. This is why customer wants another measurement to justify which DOs to delete.