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).
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.
Support Team,
Pls review and process appropriately. PowerHA has no tools to work with groups which contain thousand of users. The existing cluster command "mkgroup" produces the error while creating a group with 1,000+ users and there is no other way in PowerHA env to add users at a later time but only to do that on per-user basis, and if server has a big number of groups then we have to store the group set for each individual user in order to change user's properties which is not a trivial task and may incorporate the errors upon execution.
Also, PowerHA does not have cluster-level commands "cli_chgrpmemp / cl_chgrpmem", while adding such command helps to remediate the problem by changing the 'group' properties (group membership) instead of doing that on per-user basis. What's really convenient is that, even for large groups it is possible to split the group members into a smaller groups use cluster's "chgrpmem" command several times to add 10,000 IDs easily.
The existent command set in PowerHA does not allow to do this, leaving customers like me to struggle with per-user properties' change, which takes time and is not reliable because of a variety of groups for each user.