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 Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Mar 29, 2017

Option to have full usage history log of an object

Currently there are only 2 attributes of usage info for an object:

Last used date
Days used count

1. Last used date gives only the date used, not the time used.
2. "Days used count" does not give us which days it was used.
3. We do not know which user and job used it..

It would be a nice feature to have - optionally - a full history usage of
any given object or all objects.

Of course the programmers can write their own logs, but if it is done by the system, it is STANDARD, and any programmer can use it.

Use Case:

Build a system SQL TABLE which will conatain the following information:

System Name, Library Name, Object Name, Object Type, Date the object was Used, Time it was Used, Job Name who used the object, Job Number, Allocation type (*SHR *ECLRD etc).

Maybe to have begin and end date and time.

System Value option if to have a history log for all objects by default.

Modify the Compilers and CHGOBJD - add an option if to have a history log of the object.

Add an option to CHGLIB if the default for this library should have a history log for all object or not.

System Value for how many days to keep the log.

Value on the Library level and object level for how many days to keep the log.

The cleanup of the logs will be done automaticaly by the system.

Ability to backup the history logs.

Idea priority Low
  • Guest
    Dec 6, 2021

    .Thank you for submitting this request. IBM has no plans to pursue this change.

    The last used date is only updated once per day (the first time an object is used in a day). There are performance concerns with the additional updates needed to update the timestamp.

    Object auditing could be used to audit the use of an object. The system audit journal identifies the name of the job that generated the journal entry and the name of the
    user profile that was running. The following section in the documentation has more information on auditing:

  • Guest
    Mar 30, 2017

    It would be great if this information is included in the system clean up options. We age out objects that haven't been used in over two years so we would clean out the data older than that accordingly.