This portal is to open public enhancement requests against IBM Z Software 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.
Thank you for submitting this IMS enhancement request.
After a comprehensive review, we regret to inform you that we have determined that at this time this request will not be a candidate for inclusion in an upcoming release because the request does not appear to be technically feasible, has a high implementation cost with a low relative value, and is not consistent with the product direction. Hence, we have rejected this request.
We believe the request is not technically feasible with the current global online change architecture, because if two online changes were done while one or more of the IMSs were down, the restarting IMSs would discover that their active libraries match the active libraries in the OLCSTAT dataset and not detect that an online change was needed.
We believe the request would have a high implementation cost, because it would require completely redesigning the global online change architecture to handle the case where an IMS was down during two online changes. Users would have to ensure that an IMS's active library had not been changed since the IMS was up and that the IMS's inactive library matches the active libraries of the active IMSs. Since this would be an error-prone process, many customers may not use this function, so we think the value would be low.
The request is not consistent with the product direction of defining resources more dynamically, rather than enhancing more static resource definition functions such as online change.
We appreciate your input to the IMS development team.