This portal is to open public enhancement requests against IBM System Storage products. 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
We have implemented in R5.3 which allows a RCL to continue in the event of a failed cache drive.
We also continue to review system components for future impreovements.
This has been considered and in some instances can be done, however not in most instances. Please continue reading.
Based on other dependencies in code load, the dev team does not recommend bypassing the health check for failed drive. The development team did provide a fix for remote code load on an event that has occured a few times and this is reflected below with the enhancements in VTD_EXEC 391. This enhancement is for a SAS adapter failure that is only detected after the system boots with the new code image. As a result RCL will stop and require hardware replacement before continuing the code load. With this enhancement the user can continue the code load and replace the hardware at a later date. There are still a number of other cases where RCL would not be able to continue due to hardware but those are detectable before we start.