Skip to Main Content
IBM Power 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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - https://ideas.ibm.com/ - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

Status Future consideration
Workspace IBM i
Created by Guest
Created on Oct 20, 2020

Change the behaving of the license manager once new hardware or SN is recognized.

Problem description:

Change the behaving of the license manager once new hardware or SN is recognized.

This requirement is the outcome of my ticket TS003930677.
Together with the support engineer, we have agreed to raise an RFE and the IBM development is basically able to make research and adjust the behaving.


Use Case:

Current solution
Once we perform a failover via FSR toolkit to the secondary location and open any licensed program (like: STRSQL, WRKQRY, STRPDM, etc.) the message CPI9E77 "License key will not be valid in 71 days on MM/DD/YY" is populated in QSYSOPR. this is happening even in case the right license key ( for this secondary location) is stored in the license repository and it is applied.
However, this is highly misleading, you receive an attention message even the license keys are stored in the repository and they are valid.
To resolve this issue, you have to to apply the license keys for that current SN to be sure or wait 24 hours and run any command to invoke any licensed program (like: STRSQL, WRKQRY, GO BRMS, etc.) if the CPI9E77 appear in QSYSOPR or not.
It is due to the native behaving of the license manager; these kinds of messages are sent once per job and only once per 24 hour period.
So, if the key is missing the new CPI9E77 is sent out into QSYSOPR with a new count of remaining days. If the key is valid no message appears in QSYSOPR.

Current workaround:
No workaround in place

Proposed resolution:
Once the license manager recognized the change of hardware or SN, it will trigger an information message into QSYSOPR let say "New SN has been recognized the right keys has been applied"

In case if the key is missing it will be better to raise an attention message "New SN has been recognized however there missing right license key in the repository."
Could be acceptable to send CPI9E77 as well, but I am preferring to send this message on the next (new) day after the failover when it is clear the proper key is missing.


Idea priority High
  • Guest
    May 16, 2021

    Hi,

    the proposed solution seems to be OK.
    The most important part is the license manager will do the apply of lic. key once the SN is changed.
    Kind regards,
    //david

  • Guest
    May 14, 2021

    IBM has reviewed this request and the proposed solution.

    At this time, a solution that IBM is considering would include:

    1) Attempt to find a valid key in the license key repository before sending CPI9E77, and do not send if successfully applied.
    2) If a key is found and successfully applied, an informational CPI9E64 message will be sent.
    3) If no key is found, no additional messages will be sent, and CPI9E77 will be sent as usual.

    Also, and this would apply to some other circumstances that attempt to automatically apply license keys:
    3) If a key is found, but is NOT successfully applied, diagnostic message CPF9E82 or CPF9E74 will be sent, the key will be removed from the license key repository, informational message CPI9E5F will be sent, and CPI9E77 will be sent if this was a hardware change.

    CPI9E77 - License key will not be valid in &8 days on &9.
    CPI9E64 - License key information installed for &1.
    CPF9E82/CPF9E74 - License key not valid.
    CPI9E5F - License key information removed for &1.

    IBM does not feel it is necessary to issue a new message ID for this specific circumstance. Are there any concerns with this proposed solution from the RFE requester or community? If there are none, this RFE will be moved to Planned for Future Release status on or about May 28, 2021. The plan will be to PTF this behavior to prior releases as well.

  • Guest
    Jan 12, 2021

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. It's worth at least changing the order around to applying the license key(s) before kicking off the hardware grace period. That much alone would at least eliminate the confusing hardware grace period messages.

    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 www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager