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.
Ability to sync tables to HDR & RSS secondaries when converting from RAW to STANDARD mode.
It is significantly faster to load a table in TYPE(RAW) mode than TYPE(STANDARD) mode. However, this option is not practical for sites using HDR and/or RSS secondary servers for replication as RAW mode tables do not replicate forcing the site to b...
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...
I'm trying to check if a serial value has reached its upper limit. I noticed the following unpleasant behaviour. In the sysmaster tables sysptnhdr and sysactptnhdr the currently used serial values are in three fields for the datatypes serial, seri...
If oncheck encounters a row/table is locked it immeditely returns error:ERROR: Could not obtain lock for <database>:<user>.<table>It would be useful to have an option for user to select lock wait time for example:oncheck -cDI -lw...
Full HDR switch between primary and secondary with a single command and without any downtime
We have 2 servers with 2 HDR instances each.
For each cluster we have also 2 connection manager each.
On server one there is the primary of cluster 1 and the secondary of cluster 2
On server two there is the primary of cluster 2 and the sec...
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...
Informix documentation for oncheck command should be crystal clear
Informix documentation for oncheck command does not explain clearly that this command should be run only during a maintenance window or during an off-hours period because the oncheck utility places a shared lock on system catalog tables when the ...
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.
When we create a view using a sensible-looking query, the database converts it into a version that has lots of extra parentheses and odd-looking table names. Below is an example of one of these converted queries. This is a relatively simple exampl...
Increase supported ADMIN_MODE_USERS by moving list from onconfig to table
Parameter ADMIN_MODE_USERS handy during migrations. the ability to make the database available for a subset of users is great for post migration validation. However the length of the field (127 bytes) is a limitation that ends up being somewhat mi...
Do not place IBM confidential, company confidential, or personal information into any field.