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:

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 Future consideration
Workspace Db2 for z/OS
Created by Guest
Created on Jan 30, 2020

Improvements in online DDL changes - DBD design

Our company uses DB2 zOS almost exclusively for dynamic SQL workloads. Our management expects that DB2 zOS also has high availability regarding DDL changes in this application szenario. If you intend to perform DDL changes in this environment during online operations, there are often impacts that go beyond the object to be changed.  DDL changes such as DROPs of objects that are no longer required can lead to contention of other applications that have no connection whatsoever to the object to be deleted. This means that applications that are not directly affected by the change are also negatively affected by the change. If you analyze the interactions of workloads with dynamic SQL, you can often see that mainly the DBD design (a database forms a DBD and not a table) is the cause for the contentions. We expect a significant improvement in the current mechanisms of action with regard to DBDs similar to the transformation of the DB2 plan structure (transition from DBRMs to packages)

Needed by Date Dec 31, 2020
  • Guest
    Apr 22, 2022

    Hello Janet,

    Our management expects us to be able to roll out "simple ALTERs (ALTER TABLE ADD COLUMN)" with virtually no interruptions. In some cases, we have technical DBDs in the background that are made up of many objects. In a scenario with predominantly dynamic SQL, the small ALTER TABLE ADD COLUMN change can then lead to disruptions/hinders to the applications. We can therefore not promise our management that such small changes (ALTER TABLE ADD COLUMN) will be uninterrupted.

  • Admin
    Janet Figone
    Apr 14, 2022

    Hello Norbert, We would like to understand the scenarios a bit better. Can you update this idea with more details about the circumstances when DBD lock contention is seen?

    Thank you,

    The Db2 for z/OS team

  • Guest
    Mar 5, 2022


    please can you give us an update for the status of that idea? Is there something in DB2 V13 that helps in this area

  • Guest
    Nov 19, 2021

    We also see an increase in DBD contention. We started using CLONE tables in combination with LOAD REPLACE. We found out the hard way that the conflict on the DBD Lock, although understandable, not desirable! We now have to schedule the LOAD DATA and EXCHANGE DATA job in sequence whereas we would like to run them in parallel to improve availability of the VIEWs with UNION dependent on the tables loaded. So, a better, meaning less restricted way of handling DBD locks would be highly appreciated. We also fear that with the increasing CI/CD pipelines coming to Db2 z/OS this problem will increase as well.

  • Admin
    Janet Figone
    Nov 6, 2021

    Hello Norbert,

    Thanks for the follow up. It's no surprise that reducing DBD contention would be a popular item. Unfortunately that does not make it any easier to do. This requirement is marked for future consideration because we have a keen interest in reducing the impact of schema changes upon the system and other application threads in particular and we continue to make progress in this area. At this point though we do not have a concrete design or roadmap in place for improving the granularity of DBDs or DBD locks. If and when that changes we will update this.


    Db2 for z/OS Development

  • Guest
    Oct 28, 2021


    do you have any current plannings for that idea? Please can you give us an update for the status of that idea? I see 29 votes for that idea now and I think that this shows the relevance of that problem

    kind regards

    Norbert Wolf

    Datev eG

  • Guest
    May 14, 2021


    do you have any current plannings for that idea? Please can you give us an update for the status of that idea?

    kind regards

    Norbert Wolf

    DATEV eG

  • Guest
    Mar 19, 2021

    Hello, please can you give us an update for the status of that idea?

  • Guest
    May 7, 2020

    Dear all, we've recently opened a similar idea related by the excessive DDL Locks acquisitions but on a static SQL scenario. Please vote it if you agree, .