IBM Data and AI Ideas Portal for Customers

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

Post ideas and requests to enhance a 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 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 product management team 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Created by Guest
Created on Jul 18, 2019

Turn off the SYSLGRNX processing when reporting the activity before the modify recovery utility timestamp

We have the Situation that we keep the Image copys for 30 days and db2 archlogs for 180 days. We do a modify recovery for ICs older than the 30 days. When want to Report logrecords older than 30 days we get the message "Log records not found"  (PMR 24832.073.724). The Workaround was to bypass SYSLGRNX processing. Not all of the LAT Users are aware of the 30 days. So users may wrongly suppose that there have not been any activity on for that requested timeframe.


  • Admin
    May Chu
    Aug 3, 2021

    Delivered (UI76261 PTF)

  • Guest
    Jul 18, 2019

    In the competitor competitor tool this is already implemented.