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.
I have multiple Information Server engine tiers. I have enabled load balancing from the ISD console to take advantage of the engines. I need a way to gracefully stop one engine for maintenance, such that the in-flight transaction is processed, and still continue to process requests on the engine that is still running. The goal is to be able to stop the engine for maintenance which can vary from installing patches to updating USAC reference databases. Currently I can set the minimum number of jobs to 0 but I am prohibited from setting the maximum number of jobs to less than 1. Need to be able to stop the jobs on one server to allow maintenance while the other server(s) actively process the request.
Do not place IBM confidential, company confidential, or personal information into any field.