Skip to Main Content
IBM Power 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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

Status Under review
Workspace IBM i
Created by Guest
Created on May 18, 2022

Save timestamp captured for stream files

I would like to understand what IFS objects are NOT backed up on a regular basis. I can tell that easily with QSYS objects because the save timestamp has always been captured at the object level. For stream files, no save timestamp exists. Not everyone has BRMS which can retain object details to determine when things were saved.

Idea priority Medium
  • Guest
    Jun 10, 2022
    Thank you for submitting this request.

    To clarify, the save date/time for QSYS objects is only captured when the UPDHST parameter on the save command is set to *YES. It seems like it is always saved because the default for that parameter is *YES. Users can set it to *NO and then the save date/time will not be captured.

    Moving this to 'Under Consideration' for the team to investigate further.
  • Guest
    May 22, 2022

    Please make that Date and Time stamp of when saved.