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:



Db2 for z/OS

Showing 309

Reorg - SORTDATA NO - write to shadow instead of SYSREC and then the shadow

Reorg - SORTDATA NO - write to shadow instead of SYSREC and then the shadow
6 months ago in Db2 for z/OS 0 Future consideration

Begin / End COMMIT instrumentation for DRDA, CICS/IMS

Complex CICS/IMS or DRDA transactions (involving multiple programs with an implicit Commit at the end) are incorrectly presented on the Omegamon Accounting Report/Trace. By design the costs of the tough SYNC (COMMIT) operation are added to the las...
over 1 year ago in Db2 for z/OS 2 Future consideration

Enable customers running 24/7 to create unique indexes

Our Internet and Mobile applications are used 24/7 and we do not have any batch windows nor any maintenance windows. When creating new indexes on existing tables the a CREATE INDEX operation generates an unwanted outage when created with DEFER NO....
almost 5 years ago in Db2 for z/OS 1 Future consideration

Object should go into advisory reorg when PCTFREE, PCTFREE for update, FREEPAGE is altered instead of immediate alter to have the REORG pick it up and ensure it is done. Having it immediate is just a catalog update and it might be missed.

When Altering PCTFREE, PCTFREE for UPDATE or FREEPAGE, the DB2 catalog is updated and the DBA must ensure a reorg is run to materialize the change. A process that can be missed. I would like to see this as a pending change and have the reorg pick ...
11 months ago in Db2 for z/OS 1 Future consideration

Drop STP SQL with dependency of other STP SQL type NATIVE

We have a general purpose StoredProcedure (STPX1) that is called by other native StoredProcedures (STPA1, STPA2, STPA3, etc) that have CALL statements to STPX1, If I need DROP the STP STPX1 (for recreate later) I receive the error -478 for depend...
12 months ago in Db2 for z/OS 0 Future consideration

Prevent package invalidation after ALTER TABLE ROTATE

System: Production management databaseActor: Developers maintaining the databaseDescription: Our customer runs a 24/7 production management OLTP system with IMS V10 and DB2 V9 for z/OS on which its transaction rate gets as high as 10 trans/sec, a...
over 8 years ago in Db2 for z/OS 0 Future consideration

No Implicit Runstats when running Reorg that materializes pending DDL

When a REORG is run to materialize a pending DDL change, the REORG enforces an inline statistics (RUNSTATS) even though no statistics keywork is added to the REORG statement/card. it defaults to TABLE(ALL) INDEX(ALL).This obviously can impact acce...
5 months ago in Db2 for z/OS 0 Future consideration

Change DCLGEN to generate S9(4) COMP-5 instead of S9(4) COMP for SMALLINT columns

DCLGEN generates SMALLINT fields as S9(4) COMP with acceptable values +32767 through -32768. A Cobol 'MOVE' makes truncation possible and renders any value over 9999 risky. IBM Case Number: TS003249935
over 1 year ago in Db2 for z/OS 1 Future consideration

Ability to externalize Statistics to RTS after Runstats

In seldom cases (~1%) Online Reorgs abend because the TOTALROWS column in the SYSTABLESPACESTATS are wrong.Then we do Runstats and update the RTS.The question is, why the number of rows is not externalized after doing a RUNSTATS.The value after Ru...
7 months ago in Db2 for z/OS 2 Future consideration


With the ADD PART and ROTATE, the logical and physical partitions on a tablespace can be out of ORDER. Current REORG at PART Level is for physical partitions, and requires DBA to search catalog to find all required PARTS.
6 months ago in Db2 for z/OS 1 Future consideration