IBM Z Software
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).
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 updates on 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
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.
low priority nice to have
We (submitter) also have LPARnames that indicate the desired CEC. However, because each LPAR is assigned to a specific CEC in the SA policy, a user is assuming the correct CEC is assigned. Here is a snippet of an SA Policy source:
(S=NET5/CEC5.S502///YN),NET5
(S=NET6/CEC6.S602///YN),NET6
In our shop, LPAR S502 is defined on CEC5 and S602 on CEC6. Unfortunately, we implemented this incorrect source:
(S=NET5/CEC5.S502///YN),NET5
(S=NET6/CEC5.S602///YN),NET6 <-- S602 does not exist on CEC5.
From the panel, all looked fine. However, GDPS was trying to activate S602 on CEC5 which is not defined. This took 10 minutes to time out. We have written a REXX to do some basic validity to hopefully avoid a repeated error. Having a QUERY LPAR DETAILS would have saved resolution time.
Not something we're exposed to as we don't allow duplicate LPAR names, but can see others might like it - low priority
Low
Due to naming convention we're able to determine the CEC name from the LPAR name. But fair enough for those who can't ... low ...
This would be a nice enhancement and we could see the benefits, if ever we get into the situation requiring this RFE - Medium
We have both flavors: one location has the same LPAR names on all CECs the other location has LPAR names that contain CEC information as well. To make identification easier in the first case a CEC information on the panel would be very helpful. Pro. medium
We have a naming convention for LPAR's that enables us to uniquely determine the CEC Name from the LPAR Name. Still it is a good idea to enhance the Q (QryxDR) line command to query the current system status including CEC and IPL Information similar to what is already available for xDR for z/VM systems.
Priority: Medium
It is a nice to have feature for us since we don't have CEC name in our LPAR names.
We also have a naming standard with CEC included - low priority
We have a naming standard that includes the CEC name, so not an issue for us. Useful for those that don't! Low priority.
It seems to me that this information was available at some time in the past (probably V3R12) but I cannot find it any more.
We do have our lpars named the same on CECs in both sites in each region of our MGM4SITE, using the Normal and Abnormal site settings. However, there is some opportunity for confusion in the process of running recovery scripts for planned/unplanned site outages.
medium priority.