This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Include TIME in LAST_DATE_TIME Used object attribute
The QUSROBJD and QGYOLOBJ APIs return the so called Last Used Timestamp. The field in the QSYSINC structure is literally named Last_Date_Time. However only the DATE is returned. The request is to either: (A) If that Time is being stored to return it along with the Date information, or (B) Update the Documentation to stop referring to Last Date and Time used as "Date and Time" and make it say "Last Date used" instead.
Having the full date/time information can be useful for certain objects and especially for User Profiles. The Last SignOn is not really Last used, as if a hacker tries to use a profile to get in an fails, the Last Used Date is updated, but the Time is not updated. So it would be nice to have the time included. But short of that the documentation and interfaces need to be modified to be actual DATE values not *DTS and TimeStamp values.
Do not place IBM confidential, company confidential, or personal information into any field.