This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Automatically disable disk paths that experience repeated timeouts
IBM i is not able to intelligently avoid repeatedly using non-functioning disk paths that identify themselves as functional. Repeated I/O timeouts cause long periods of disruption and very poor performance often resulting in abnormal termination of interactive user and batch jobs.
Paths can and do fail, which is why it is a best practice to configure hardware redundancy in the host, SAN, and storage subsystem levels. This redundancy comes at a prices, but IBM i is not taking advantage of it on certain path failures. Currently, when a path fails, IBM i will repeatedly attempt to use a nonfunctional path, and this can cause long periods (hours) of very poor system performance if no outside action is taken. It also makes sense to include robust error handling in the software (IBM i). IBM i should be changed so that the device driver automatically disables paths that experience 2-3 timeouts in rapid succession. Ideally, the driver would send a message to QSYSOPR pending retry. After SAN maintenance has been completed, the message would be retried and paths would go active again. In this method, users can control the retries, similar to a communication line failure, and not have the system continually attempt to use a non-usable path.
Do not place IBM confidential, company confidential, or personal information into any field.