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 re-create views and procedures without dependent objects being dropped
Some objects in a database often depend on other. As an example, if there is a view, another view can be built upon it.Private and public synonyms can be created for those views, and permissions given to various users on those views.If the first v...
Since the improved readahead code was established, onstat -p and the associated SMI tables no longer report all readahead pages nor all usage of those pages so that it is impossible to monitor the efficiency of readahead and so be able to determin...
Allow Informix to kill sessions not only limited by session-id
Informix should be able to kill sessions not only limited by session-id:For example: If a admin should kill sessions from a specific user or host a script is needed.So it would be helpfull if onmode -z would accept following syntax for example:$ o...
Config for the server to refuse to start if shared memory segments do not use huge pages.
When shared memory segments are not using huge pages there can be performance impactI would like an option for the engine to abort startup similar to FULL_DISK_INIT=0 if huge pages cannot be used for shared memory segments. Scenario: sysmaster sy...
Support IDataReader::GetBytes / IfxDataReader::GetBytes for BSON fields
We're using the BSON capabilities of the Informix server in order to store data in a separate BSON colum - like additional information for the data row or optional fields that may vary from row to row (e.g. translations to different languages).Wit...
Many organizations use unified approach to collecting, storing and visualizing metrics from various sources using at least one of the few established platforms of which Prometheus+Grafana are probably the most prominent. It would be very beneficia...
almost 2 years ago
HQ add essential incidents/events/status tracking and alerting
HQ is on its way to be a great monitoring tool. In order to ensure it is, here are some important features to add (not sure I could see them on FC3).
Let's first deal with missing essential alerts:- include notion of warning and critical incident...
Permit blocking checkpoints on secondary nodes when raw tables exist on the primary node.
Currently we cannot issue a blocked checkpoint on a secondary (RSS in our case) when there exists raw tables on the primary node.We use raw tables heavily for admin jobs (mostly for the selection processing of archiving/purging jobs) to avoid swam...
Allow the specification of the isolation mode at the statement level
The programmer should be able to specify the isolation mode (committed read, dirty read, serializable etc.) at the statement level.I don't have a definitive idea on how to specify this in terms of syntax. It could be in a "clean" way like:SELECT ....
Do not place IBM confidential, company confidential, or personal information into any field.