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 Planned for future release
Created by Guest
Created on Nov 14, 2019

Provide a way to run CM Batch with CAF, so that the RRS limitation is bypassed and DSNREXX can be used in REXX verification exits.

The costumer's DBA team want to avoid any new tablespace creation not using Partitioned by Grouth Universal Tablespaces.

As MAXPARTTITIONS is not a suitable override mask, we try using a REXX verification mask in the form:


So a REXX ADBDSIZE located in ADBUEXEC receive the parameters and can force depending on the return code to fail the verification if the object is not already defined in the target DB2 subsystem.

We found that a REXX verification exit can not connect to DB2 using DSNREXX, so any verification based on the atributes on an existing object can not be implemented easylly.