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 Not under consideration
Workspace IBM i
Created by Guest
Created on Jun 3, 2016

Revamp Open Source installs

Currently the installation of open source (Node.js) has two very unfortunate consequences.

1 - I have to IPL my machine.
2 - It wipes out previous version (i.e. 0.12.12 will be wiped out by 0.12.13 of Node.js)

This makes it very laborious and risky to upgrade version. Laborious because IPLing a machine isn't a 1 minute thing, and risky because I don't know if the new version will cause issues.

Use Case:

My recommendation is to allow multiple versions of open source exist in IFS and developer can alter PATH and LIBPATH to dictate what should be used. In this way we follow how Linux platforms work and lessen the number of surprises.

Idea priority High
  • Guest
    Apr 4, 2018

    .Open source technology is now available through a completely new install mechanism (RPM's). More information can be found here:

    These RPM's address your primary concerns, as the install of open source is now greatly simplified. It is also chroot-friendly, so you can preserve old versions of open source packages by simply installing the new version into a separate chroot jail. However, since we are not currently (or planning to) ship an archive of all past releases, this RFE is being marked as "declined."

  • Guest
    Aug 15, 2016

    I've since learned I had a wrong perception of needing to IPL. Thanks for clarifying.

    Concerning only doing major versions as separately installable... I think it's important to look at the reason there are minor versions after a major version; namely, bugs. Each bug fix could introduce new bugs and I should be able to easily do a/b testing before I move my code forward to a new version.

    It would be great to eventually get to the point of using tools like/similar to nvm (

  • Guest
    Jul 8, 2016

    IBM will provide multiple installable versions only for major versions that affect compatibility (such as Node 0.12 alongside Node 4.0 or Python 2 alongside Python 3). Minor bugfix versions will not be made to be co-installable. Regarding IPL issues, none of the OPS PTFs should require an IPL. If you continue to have IPL issues, please contact IBM support in the future

  • Guest
    Jun 15, 2016

    I have not experienced having to IPL to install the PTF's for node.

    But I back the request to be able to have different versions of node (and the other OSS) installed concurrently. This will make testing new versions and fallback to previous versions much easier.

  • Guest
    Jun 4, 2016

    Creating a new RFE based on Community RFE #89473 in product IBM i.