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.
Compress statement text before insert in Dynamic Statement Cache
GGDB212006'Compress' statement text of dynamic SQL statements by removing all unnecessary blanks before inserting in DSC. As a consequence statements have to be 'compressed' before comparing it to statements in DSC
Our company uses DB2 zOS almost exclusively for dynamic SQL workloads. Our management expects that DB2 zOS also has high availability regarding DDL changes in this application szenario. If you intend to perform DDL changes in this environment duri...
Since V10 there is implicit casting, which is one hand a good feature, but on the other hand can lead to big performance problems. Improve the implicit casting so that the resulting datatype is indexable, e.g. make SELECT ... FROM T1 WHERE Integer...
As mentioned in Case TS004024647 there are some situations where inserts in lob structures do not provide the expected performance. Instead they cause massive CPU consumption in the Coupling Facility for the spacemap search.The problem is excessi...
Create INDEX and SKPT lock. DDL and continuous availability.
Working in a banking 24x7 environment without any maintenance window our concurrency issues with DDL changes are increasing more and more everyday as our workload increases.There are some concurrency problems that we think it should value the effo...
When using REOPT(ALWAYS) on a batch package to deliberately avoid filling the Dynamic Statement Cache (DSC) the SQL is, correctly, not inserted into the DSC and is not exrternalized by an IFCID 316. However this then "hides" the workload from moni...
Standardize and allow LISTDEF PARTEVEL syntax for MODIFY STATISTICS utility
Currently MODIFY STATISTICS utility does not support LISTDEF with PARTLEVEL and throws an error like in example:LISTDEF DB2RK INCLUDE TABLESPACE DS0HUZX.S0HU37P PARTLEVEL(20) TEMPLATE COPYIC DSN(&SS..ICR.&DB..&TS..P&PA..&UQ.) T...
Hello Db2 for Z/OS Development.Apar PM89016 was created several years ago to implement the lock avoidance for singleton SELECTs with ISO(CS) and CD(YES) when R-scan is used, or the index that is chosen has matching predicates on all columns of th...
Profile Tables today support only remote connections and no support for local/batch applications. When PT is used to set certain registers, it only works for remote applications and local apps needs to be changed to add certain SET commands.
issue DISPLAY BLOCKERS instead of DISPLAY CLAIMERS when DRAIN timeout
Currently when DRAIN fails during REORG, a DISPLAY CLAIMERS is issued. The draw back is there is no "age" information, so user does not know which thread is the blocker, because the claimer could also be waiter.
Do not place IBM confidential, company confidential, or personal information into any field.