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 Future consideration
Created by Guest
Created on May 16, 2013

Ability to add columns to DB2 z/OS tables without impacting IDAA or incremental update

Currently, adding a column to a DB2 z/OS table that is using IDAA with incremental update involves:

1) Adding the column in DB2 z/OS
2) Stopping replication for all IDAA tables
3) Dropping the affected table from IDAA
4) Adding the affected table back to IDAA
5) Restarting replication, which first forces a full reload of the affected table.

I am requesting that this process be simplified to:

1) Add the new column to the DB2 z/OS table

That's it. There should be no need to drop/add tables to IDAA. There should be no need to manually stop/start replication, and there should be no need to do a reload.

With CDC from DB2 z/OS to other types of target databases, we accomplish this with the following steps. IDAA should automate most of this. It does require ADDCOLUMNISSCHEMACHANGE=YES and ONSCHEMACHANGE=STOP parameters for CDC z/OS.

1 - Applications touching the table to modified are quiesced. (Manual process)
2- The add column is performed to the DB2 z/OS table. (Manual process)
3- When CDC sees the add column in the DB log, it stops replication for the CDC subscription. (Automatic within CDC today)
5 - The target table is altered to add the same column (IDAA should automate this)
6 - A refresh of the CDC metadata for the source and target tables is performed. (this function is available in the CDC access server java API and this should be automated by IDAA)
7 - The subscription is restarted. (Should be automated by IDAA).
8 - Applications are allowed back in. (Manual process - but I would suggest that the subscription start message could be trapped by the customer to know when everything is ready for application access)