Skip to Main Content
IBM Power Ideas Portal

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Workspace AIX
Created by Guest
Created on Nov 30, 2022

nimadm with option to migrate multiple lpars at once

In our environment we have more than 400 active lpars to migrate to AIX 7.3 soon.
For the migration we only have six month time and only one day a week. So we have to migrate multiple systems simultanious. Unfortunately, there is no build-in way to do this with nimadm.
In the moment I have to do it with nohup or GNU parallel. Both ways are not very ressource friendly. Simultanious migration on only four lpars causing 100% cpu usage for 45 min and the nimadm processes using only two threads per process. Some tests showed that I would need one physical core per lpar migration to speed up the migration by 10 to 20%.
This is not a good ressource management...
It would be great to have the functionality to parallize the migration within nimadm. Maby by giving a mac_group or multiple systems at one like nimadm -C mac_group or nimadm -c lpar1 -c lpar2 -c lparx ...

Best regards,

Idea priority Medium