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
Created by Guest
Created on Mar 15, 2019

DB2 Administration Create MIG Data job in Batch with no foreground input required

For automation we require the ability to generate MIG with DATA via a batch job with no foreground input. This is to enable the whole process to be automated via zosmf workflows.

So, for instance, there may be a requirement to generate unloads and loads for thousands of tables. We wish to be able to provide the list of tables via a file to a generate job which will then create the unload /load jobs.

Currently, you have to create an object selection list in Admin Tool. You can then generate a batch job which will then generate the unloads and loads. We want to effectively replace step one where instead the object selection is provided in a file.

Without this we have no way to provide a dev ops solution without writing our own rexxes to manipulate the Admin Tool ispf tables directly. This is, for obvious reasons, something that we want to avoid having to do.

Although important for dev ops, this is also important for other automation such as generating unloads and loads from production to test and creating 'backups' of test environments when image copies cannot be used due to table structure  changes.