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 (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
  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 (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.

Status Needs more information
Workspace AIX
Created by Guest
Created on Apr 28, 2026

Full Automation of AIX "autofsinstall" via system defined lpp_source

AIX 7.3 TL4 introduced the 'autofsinstall' functionality, which enables the automatic installation of missing packages. While this feature significantly streamlines operations, it currently requires the manual mounting of an 'lpp_source' from the NIM server prior to use.

To further enhance this workflow, it would be highly beneficial to introduce a system variable to store the designated lpp_source. Ideally, the autofsinstall mechanism should leverage this variable to automatically handle the allocation and deallocation of NIM resources. This improvement would eliminate the need for manual intervention, providing a fully automated package management experience.

Idea priority Medium
  • Guest
    May 19, 2026
    if the user allocates an lpp_source, that should already be sufficient for the current autofsinstall workflow. When a command is not found, the system automatically searches the previously allocated lpp_source, identifies the required fileset, and installs it successfully.
    In addition, the allocated lpp_source remains associated with the client even after the installation completes, effectively retaining the software source for future requests as well.


    Example:
    nimclient -o allocate -a lpp_source=AIX73TL4SP0
    nslookup
    ksh: nslookup: not found.
    nslookup belongs to fileset bind.rte. It's not installed on the system. Do you want to install it? (y/Yes).
    y
    Installation Summary
    bind.rte 7.3.918.2802 APPLY SUCCESS
    bind.rte for command nslookup successful.


    Given this behavior, the existing allocation mechanism already appears to address the requirement of identifying and retaining the designated lpp_source.
    Would you still see value in introducing a separate system variable for the lpp_source? If so, could you please share the additional use case or scenario you have in mind beyond the current functionality?