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.
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 database is checked and that the shared lock prevents any other updates, inserts, or deletes on the database until the check has completed. Various aspects of this information are found on a variety of sources of IBM documentation, but the information is not expressed clearly on the page that is intended to describe this command. I had to ask Informix Support multiple questions before I could get the answer I needed. Previously I had the oncheck command running on our production machine on Sundays, but even then it would sometimes cause problems for other production applications that were running on that day.
Do not place IBM confidential, company confidential, or personal information into any field.