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 Not under consideration
Workspace AIX
Created by Guest
Created on Jul 23, 2015

Change AIX update process to exclude updating Perl and or just it's external modules

Currently when an Admin goes to upgrade AIX (ie. TL/SP levels),
the upgrade process also will update perl runtime along with man pages. This process will at times overlay/"backlevel" modules which have manually been added to the perl (from CPAN) in order to support some function, (ie. Spreadsheet xlsx). Thus the perl program using this "once installed" modules will abort. The Admin will then have to track down, and re-install the module. THis is very time consuming,tedious, and troubleshooting to identify the "backleveled" module is extremely difficult. WHen in a production environment, this is un-acceptable.

Idea priority Medium
  • Guest
    May 1, 2017

    It's not a good idea for a user to replace files installed as part of an
    installp package (whether perl.rte or any package at all). This can make
    it appear to the system that there is a corruption in the fileset, and it
    may have unintended consequences if some other utility is specifically
    dependent on the original version of the file, if there is a possible
    compatibility change. Also there is the issue cited here: an update to
    that fileset for maintenance will overwrite a modified file with the
    original copy.

    It is more appropriate to put one's own copies of alternate versions of files
    into another path, and point to those versions where needed. For perl, one
    way to do this is to have a local directory with different desired versions
    of modules, and point the PERL5LIB environment variable to the top of this path.

    Another option with AIX is to install the latest version of Perl from the
    "AIX Toolbox" website, which gives the user access to a newer version of Perl
    than is provided on the AIX operating system media. This version installs
    into a different path, so users can choose between the fixed stable version
    provided with the OS or the newer optional updated version provided with the
    Toolbox.

    No special provisions are planned for perl.rte with respect to system updates.

  • Guest
    Jul 27, 2015

    Creating a new RFE based on Community RFE #74510 in product IBM AIX.