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.
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 b...
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.
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...
Hi,my customer is a long haul IDS customer who loves it. A few years ago, his team fell in love with Tableau, which resolved many business cases for his company.Unfortunately, after getting more and more demanding with Tableau functionality, and c...
Add SQL-statement COMMENT ON as in Oracle or PostgreSQL
For some tables or columns it would be helpful to describe what the table/column is used for since the names are not always self-explanatory.Although COMMENT ON is not part of standard SQL it would be helpful to have such a statement. The DOCUMENT...
Allow DDL changes on a table with full row logging
We want to use CDC to replicate data changes to a different system. We do schema changes once a month, and this complicates things a lot. According to our vendor, this is a limitation for Informix only, other source systems can hande DDL changes t...
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 ...
Add metrics for reverse index scans and number of retries.
As per APAR IT37120: CONCURRENT QUERIES USING REVERSE SCAN OF INDEX WITH MANY DELETEDENTRIES MAY ENCOUNTER POOR PERFORMANCE
reverse index scans can require a retry.
Add metrics for number of reverse scans per partition and number of retries.
Allow placement of tablespace BYTE and TEXT data in a separate dbspace from the table's base row data.
Allow specifying a normal dbspace for a BYTE or TEXT column to isolate IOs for the blob data from main row data for the table. This would be logged space just like IN TABLE as opposed to IN blobspace blob pages.
Do not place IBM confidential, company confidential, or personal information into any field.