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 Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Jun 4, 2019

Add commit frequency to Modify Recovery utility

If there a numerous rows in SYSCOPY to be modified out the modify job holds locks on SYSCOPY for an extended period of time and can cause timeouts for other processes and utilities that are using SYSCOPY

  • Admin
    Janet Figone
    Dec 18, 2020

    Thank you for submitting this request. Db2 for z/OS development has reviewed it and determined that because rows are deleted in descending timestamp order, we cannot introduce intermediate commits without risking causing recoverability issues. However, the genesis of this requirement is that MODIFY RECOVERY should be non-disruptive. We are investigating the locking algorithm for MODIFY RECOVERY on SYSCOPY and will take further action if necessary to prevent deletes of older rows from impacting insert or update of newer rows in the table.

    Sincerely,

    Db2 for z/OS Development