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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Using the license management APIs QLZAGENK & QLZAREQ, once a permanent key is provided to a customer (expiration date *NONE), there is no way to retract that key when a customer wants to transfer their software license to a new CPU. The result is customers can run the software on both the old and new CPUs, essentially getting free software (albeit in violation of their software agreement). Current workaround: Provide temporary license keys only, however this tends to upset customers expecting a permanent license key. Another solution is to allocate a dummy license user that cant be released, however that creates an accounting nightmare on partitioned systems. Proposed resolution: Provide a new license management API that allows a license key to be invalidated. The API could produce a new 'uninstall' license key as output (perhaps using the vendor data field), which the customer could email to the vendor as proof the uninstall was performed. Vendor could verify the uninstall license key, then provide new permanent keys for the new CPU #.
Do not place IBM confidential, company confidential, or personal information into any field.