This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
Per not from JPMC - Ovidio Ruiz on April 10, 2017 " we have no need to continue to keep this RFE opened. The RFE can be closed." Sorry for the delay in actually closing the request. THANKS for the input !
Thanks for your input. I think we need to address your request in 3 different categories.
The properties you listed (initial_processing_weight, initial_ziip_processing_weight, current_processing_weight_capped) are not possible to directly change the current_processing_weight_capped or any of the "current_" properties on a running LPAR. But, what you do instead, is you change initial_processing_weight_capped via the WS API (or the User Interface) and then when the operation completes, the current_processing_weight_capped is also changed. You don't need to be able to change the "current_" values but instead you change "initial_" values and the "current_" ones will automatically be updated as well.
Two of the properties you listed (central_storage, reserved_central_storage) are not possible with the current IBM z System Architecture, and the current hardware and software implementations.
Lastly, you asked about being able to update the number of processors in a live, running LPAR via WS APIs, or more specifically these properties:
number_shared_general_purpose_processors
number_reserved_shared_general_purpose_processors
number_shared_ziip_processors
number_reserved_shared_ziip_processors
Today there is an existing User Interface task that can increase the values for a running LPAR, but the current IBM z System architecture and implementation can not support decreasing the values on a running LPAR. We can look at WS API support to be able to increase the values equivalent to the existing UI task in a future system. Would just being able to increase the values be ok and if so, what priority do you want?
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Hardware
Product - z Systems Hardware
Component - HMC/Support Element (SE)
Operating system - Other
Source - Other
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - Power Hardware Management Console
Component - Product functionality
Operating system - Other
Source - Other
Creating a new RFE based on Community RFE #90231 in product Power Hardware Management Console.