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).
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 updateson 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
Support for multiple clients in NIM customization command
It's highly desirable for system administrators to have a way to use NIM functionality to manage multiple systems, often on an ad-hoc basis. In particular, NIM scripts can be very useful for automating tasks across multiple AIX clients, but currently the command only allows for a single client or group as the target of the operation:
/usr/lpp/bos.sysmgt/nim/methods/m_cust -a script=ScriptName TargetMachineOrGroup
In many occasions a preconceived client group may be of use, but there are plenty of occasions where one might desire to run a script against a specific set of clients that don't fit the mold of a logically organized group - for example, to gather logs from a random set of servers experiencing issues after a network event, or to reset a user password on a subset of systems the user happened not to have touched recently and therefore their password expired. I could see this being quite useful in other scripts where a programmatically generated list of systems based on certain conditions would be useful. It seem onerous that to get this functionality we either need to craft "for" loops on the command-line, or create ad-hoc groups as needed every day. On the other hand, this seems fairly easy to build into the command itself (perhaps a new argument that accepts a list or an input file). Ideally this would also be baked into a SMIT menu for even more convenient ease-of-use.
Do not place IBM confidential, company confidential, or personal information into any field.