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.
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.) ...
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.
Currently the IFCIDs 316 and 401 contains great data for monitoring and tuning SQLs. It would be excellent if these IFCIDs could be extended to include a separate set of ZiiP counters. IFCID 25 does this for Utilities at the moment.
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.
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....
almost 2 years ago
in Db2 for z/OS
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...
Log offload task needs to be manually cancelled restarted after outage to tape
We are seeing situations when tape processing is down and a DB2 request to offload logs to tape is initiated using dynamic allocation, that offload task will hang and never be satisfied until the offload task is cancelled and re-driven manually. T...
Allow 3 different options for statement concentration.
We would like 3 options for statement concentration. It is importantthat all three options are available. 1. No concentration. (already exists) 2. Concentrate queries that have no parameter markers (Current DB2 concentration) 3. Concentrate querie...
support list partitioning - Range-Partitioning allows only to define the upper limit for a partitioned Tablespace.
Full Support for LIST-Partitioning required! With classical Partitioning or UTS Partion-by-Range you can only define the upper limits (key-Ranges) for a partitioned Tablespace. The lower partition-range ist defined by the highest value of the next...
Do not place IBM confidential, company confidential, or personal information into any field.