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 Functionality already exists
Created by Guest
Created on Sep 28, 2020

Allow COPY with Templates to pick TAPE or DASD based on RTS

We are creating intraday Image Copy jobs that may contain a mix of small and large tables. We use Templates and Include/Exclude to determine which objects should go to TAPE and which should go to DASD. The threshold for what determines large or small is currently an agreed upon number within the group. For any one database we have a two-step job with one step for DASD and one for TAPE. Ideally we would want everything to go to DASD but we are limiting the size of our DASD pools at the moment. We would like this process to be self-managing to recognize the addition/removal of tablespaces/indexes as well as when the threshold for any given object is exceeded. Today determining which step a table should go in is a manual process

Needed by Date Jul 31, 2021
  • Guest
    Dec 9, 2020


    Thanks for your response via email that this functionality already exists. To save us just a bit of time can you point us to the correct v12 manual and page so we know we are looking in the same place as you are. Without having looked yet, I assume it's in the Utility Reference manual but I just want to make sure we are both looking at the same manual.