Skip to Main Content
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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Delivered
Created by Guest
Created on Sep 7, 2019

Db2 archive log mode(quiesce)

Reference to Case number TS002663644

This is for using "Db2 Recovery Expert disaster recovery feature - Recovering at the remote site using DB2 image copies":

During Disaster Recovery tests some Db2 subsystems found indoubt and inflight threads at Db2 subsystem startup and, as result, some of db2 objects ran on Logical Page List (RW,LPL) status. To fix that we manually ran RECOVERY INDOUBT command to get rid of IMS thread found. DBAs ran idcams to define the underlying VSAM LDS that was missing, ran Db2 command -start db() sp(<spacenam) acc (rw) followed by recovery tablespace utility. These are manual intervention and we are looking a way to avoid those indoubt / inflight threads, thus avoid LPL. 

It seems the dRE product currently does a simple -ARCHIVE LOG command during DR prep1 job execution and by adding  -ARCHIVE LOG MODE(QUIESCE) in the archive process should help in avoiding those indoubt/inflight threads.

Needed by Date Dec 31, 2019
  • Guest
    Mar 21, 2020

    In progress Track PH20428