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,
Post an idea
Upvote ideas that matter most to you
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.
Improve messaging surrounding the +20272 SQL warning in cases of a -904
A DBA was running an ALTER NOT CLUSTER. The ALTER should have converted the tablespace to table-controlled partitioning, but it encountered a -904. I have copied the output to "additional details".In the SPUFI output, after the -904, the ALTER dis...
Allow for "OPTIMIZE FOR n ROWS" to be added to DELETE, UPDATE Statements
OPTIMIZE FOR 1 ROW can be added to SELECT SQL. One reason may be to influence the optimizer to chose one index over another, or to not perform a SORT with List Prefetch Adding OPTIMIZE FOR 1 ROW to a DELETE statement results in an error: EXPLA...
Reorging a TS with NPSIs, SORT NPSI = AUTO, getting IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR which resulted in DSNU3341I 171 01:39:59.85 DSNURPCT - CANNOT ALLOCATE SORT DATASETS WITHIN 255 LIMIT , REORG should change to SORTNPSI = NO to prevent abend
Reorg TS with NPSIs and SORTNPSI or zparm REORG_PART_SORT_NPSI = AUTO. Reorg decides to run with SORTNPSI YES which sorts all keys for NPSIs. Job is having issues getting DASD resulting in numerous:01.39.58 J0916868 IGD17272I VOLUME SELECTION H...
Db2 REST services, with versioning enabled, sets the first service created via the BIND SERVICE command to be the default service.at this stage the URL and the REST service are in sync and the URL need not reference the version as DB2 will invoke ...
Distributed Thread cancelled due to Idle Thread Timeout or MONITOR IDLE THREADS not writing record to SYS1.LOGREC
We noticed that every DB2 distributed thread that is cancelled because:
1) Idle thread timeout value that is specified by Db2 subsystem parameter IDTHTOIN in macro DSN6FAC is exceeded; or
2) ATTRIBUTE2 value in a row with KEYWORD value MONITOR...
IBM Db2 z/OS development team to allow different column names in different parts of a UNION clause, as long as their types match, and assign the column names from the first part of the UNION clause to the columns of resulting table
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...
Do not place IBM confidential, company confidential, or personal information into any field.