Skip to Main Content
IBM Power Ideas Portal

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace IBM i
Categories Core OS
Created by Guest
Created on Aug 12, 2021

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.

Use Case:

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.

Idea priority Medium
  • Guest
    Jun 23, 2022

    Thank you. I've read the corrected documentation and it is very clear and helpful.

  • Guest
    May 3, 2022
    The definition of the Last-used date field has been updated in the following Object-related APIs:
    Open List of Objects (QGYOLOBJ)
    List Objects (QUSLOBJ)
    Retrieve Object Description (QUSROBJD)

    The changes were made in IBM i documentation in versions 7.5, 7.4 and 7.3.

    IBM Power Systems Development
  • Guest
    Nov 5, 2021

    Moving out of submitted status for making the suggested documentation update.

  • Guest
    Sep 2, 2021

    Note: After consulting with "the Lab" it was determined that this request is not viable.
    The existing *DTS format returns both date and time information, however the Last Date/Time Used information has erroneous Time data that should be discarded. The APIs that do not discard it (set it to 0) return one of the fixed times rather than the actual time the object was last used.
    IBM said they will update the Documentation, and that users should discard the time component from those APIs that return that information--using only the date portion of the *DTS value.