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 Dec 17, 2016

IBM should "open source" the source code for LPPs when they are withdrawn from marketing

Over the years, I have seen several IBM LPPs for OS/400 (now IBM i) that were withdrawn from marketing and eventually had support dropped -- for whatever reasons.

I think it would be a great way for IBM to educate the world on how to build robust applications for IBM i, especially in the "native" ILE environment, by delivering the source code for IBM software products that IBM no longer sells or supports, as "open source", publishing that source in some public repository like github, etc.

Use Case:

This would allow customers who relied on the withdrawn products to "take over" maintaining that product, in-house, if needed, for a period of time, until such a time as those applications they developed that depended on that LPP can be migrated to some other technology.

This would also serve as excellent educational material, for both IBM customers and for colleges and universities who want t o study some "large scale" and "real world" applications code on IBM platforms.

Providing source code for "abandoned" LPPs could help to prevent IBM customers who were depending on "withdrawn" and "no longer supported" LPPs from just abandoning the IBM i platform altogether, and migrating to some other hardware platform(s) and Operating Systems and other vendor software platforms..

This would also offer the possibility for IBM business partners to "step in" and "step up to the plate" and take over providing software support and possibly even future enhancements for those "abandoned" LPPs ("abandonware") for those other IBM customers who w ere using and depending on those LPPs.

Idea priority High
  • Guest
    Dec 17, 2018

    Interesting request, but IBM does not intend to provide a solution at this time. This RFE is being closed.

  • Guest
    Jul 24, 2018

    The CAAC has reviewed this requirement and recommends that IBM not implement this request. IBM should not spend resource on this -- it is not likely a good educational value. A vendor could just approach IBM to take over a retired LPP rather than giving it to the community.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see

    For more details about CAAC's role with RFEs, see

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Dec 19, 2016

    I realise that pretty much every LPP is built with very custom tools, and may be written in a very custom language. Despite that, it is still useful for the community to have access to this code base, if only to be able to assist in porting it to an OSS build chain.