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.
For lock spinslocks show if loops are for read or writes
When reviewing onstat -g spi for lock spinlocks e.g. Num Waits Num Loops Avg Loop/Wait Name 433407 127960809035 295243.98 fast mutex, lockhash I would be great to know if this access is for reading or writing so we can determine if this is ap...
For buffer spinslocks show if loops are for read or writes
When reviewing onstat -g spi for buffer spinlocks e.g. fast mutex, 3:bf fast mutex, 3:bhash It would be great if we could tell if this is from either: a) Read access i.e. more app caching/better query plans/more data archiving+purgin needed ...
Currently the syntax to define a trusted context accepts only IP's . In view that microservices are deployed on Kubernetes infrastructures, the DBA has to add all the IP's of the different subnets. This is both cumbersome and laborious. The propos...
This feature is about having native support to version data within the table. The application will always be able to access the most current data, however through pseudo columns or via other means older version of the data is available. This featu...
When no suitable index is created, the optimizer does an "auto create index" for the query. This proposed index should be printed out to the online.log to help the admin to create the optimized indexes for the queries.
Document "autotune" paramerer for cpu and aio in the onconfig.std file.
Its is not easy to find any document that cover all three of 1) AUTO_TUNE 2) VPCLASS cpu,autotune,noage and 3) VPCLASS aio,autotune=1,noage. The onconfig.std file does not even mention "autotune", yet this is the best place to concisely let it be ...
Expand DELETE syntax implementing LIMIT clause and maybe also ORDER BY. Delete syntax can be like: DELETE [FROM] tbl_name [WHERE where_condition ] [ORDER BY ...] [LIMIT row_count ] This limit + order by syntax is already implemented in other major...
Allow MAX_PDQPRIORITY to be configurable per user.
We want to Informix to be able to use PDQ but we would not want 3rd party logins to be able to use PDQ and impact processing. The existing onconfig parmeter should be a default is it is not defined for the user.
Implement CREATE OR REPLACE option for triggers/views/synonyms/row types
Since a similar option for stored procedures is available starting with version 14.10 it would be handy if this syntax could also be introduced for triggers, views, synonyms and row types. Currently you first have to drop a trigger/view/synonym or...
When removing unused indexes the first step we want is to be able to make index invisible to queries similar to the Oracle feature. As the index is still being maintained the rollback to make the index visible to queries is quick.
Do not place IBM confidential, company confidential, or personal information into any field.