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 Future consideration
Created by Guest
Created on Nov 7, 2018

"Change Licensed Internal Code" needs to verify that a given release is supported on the target system

Per FixCentral, AL710 and AL730 are the only two firmware releases for an 8233-E8B (and level 159 is the "end of the line" for release AL730). However, "Change Licensed Internal Code for the Current Release" reports that "There is a new upgrade release available at the repository."

Rather than simply checking for newer levels of firmware, the HMC should also verify whether any newer levels are in fact supported on the target system. The message an end user ultimately receives should be something along the lines of either "you are already at the latest supported firmware for this system, no action is required on your part" or "you are currently at level X, the latest
level supported by this system is Y" (even if there's a Z available).

See Case number TS001566729 for more details.

Idea priority Medium
  • Guest
    Nov 8, 2018

    Hello. This is an item we have discussed in the past and over a few iterations, the latest iteration of this puts all system support validation on the firmware side. It's rare but not unheard of for offering management to add support for a system to a firmware stream after being released. And if we control the blocks in the HMC itself, it would prevent users from installing that firmware as updating an HMC is much more rare than updating firmware. I'll have a discussion with some of the server-side engineering and release teams to see if we can meet a little closer in the middle.