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

If you have not registered on this portal please register at . To complete registration you will need to open the email you will receive from Aha to confirm your identity.

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:



Db2 for z/OS

Showing 370

Altering the default value of a global variable

Global Variables: A global variable can be created with a default value. Each session that uses it will then instantiate a version of that global variable, with the default value and any change in the value is limited in scope to its unit-of-work....
about 1 year ago in Db2 for z/OS 1 Not under consideration


Message for LOG MSTR of the command START DATABASE and STOP DATABASE.
8 months ago in Db2 for z/OS 1 Not under consideration

Full Column Match and I1 Access on SQL with Correlated Sub-Queries Containing Column Expressions and Supporting IoE

Some queries with column expressions - DATE(A1.EFCTV_TS) <= DATE('04/05/2020') for example, and an Index on Expression to support the expression are achieving I1 access while others are not. It appears this is because of how the query is curre...
about 1 year ago in Db2 for z/OS 2 Not under consideration

Improve persistent thread concurrency

With the implementation of transactions with persistent threads (like pseudo wait-for-input on IMS) we have been facing some concurrency issues in our site, specially with HPU and batch programs that perform lock escalation. This happens because t...
about 2 years ago in Db2 for z/OS 5 Not under consideration

Add more granularity to commands -START PROFILE and -STOP PROFILE

Summary: Enable a new keyword PROFILEID(list-of-profile-IDs) for the -START PROFILE and -STOP PROFILE commands.----Currently, the activation of profiles can be performed by a -START PROFILE command, which in turn activates all profiles that have S...
almost 3 years ago in Db2 for z/OS 1 Not under consideration

EXPLAIN PACKAGE - Populate all EXPLAIN tables

EXPLAIN PACKAGE only populates the PLAN_TABLE It should allow for the population of explain tables
2 months ago in Db2 for z/OS 1 Not under consideration

Allow column masking on system temporal tables

We have a few System Temporal tables that have sensitive data. We need to be able to create column masks on those columns. Currently we get a SQL20474N with Reason Code 17 when we try to run a CREATE MASK on system temporal tables.
9 months ago in Db2 for z/OS 1 Not under consideration


Provide for a SCOPE(GROUP) option for START/STOP PROFILE commands similar to START/STOP PROCEDURE.
over 3 years ago in Db2 for z/OS 2 Not under consideration

Allow RUNSTATS SHRLEVEL CHANGE to operate as the name says

This RFE is a result of the PMRs (31614,112,848) we have opened where the root cause was identified as invalid values in RTS tables. Current design allows to re-initialize certain fields in RTS (eg. TOTALROWS) only by executing RUNSTATS SHRLEVEL R...
over 2 years ago in Db2 for z/OS 2 Not under consideration

Add new STATUS codes to SYSIBM.SYSTABLESPACE to reflect different states of the tablespace

For the person who wants to identify the tablespaces that are in advisory reorg-pending status to collectively identify those tables and include them collectively in a reorganization job.
4 months ago in Db2 for z/OS 6 Not under consideration