This is a blog about 2 examples where IBM users encountered unexpected delays and expense to get the needed software keys when they replaced their donor servers with newer servers.
Anyone familiar with installing IBM i software is familiar with software keys.
As a quick reminder, software keys certify you have IBM authorization to use IBM licensed software on a serialized server in your enterprise. Without the software keys, the IBM software will stop working within 70 days of installation.
In most cases, IBM software keys are straight-forward. You either load them after you install new IBM software, when you complete a version upgrade, or when you upgrade to a new IBM server.
There are other cases when it is a whole lot trickier. Here are two examples I was recently involved with.
Software Developer Upgrades To POWER8 And Discovers Their Keys Are Not Permanent
A software developer had purchased an IBM POWER6 under a special program that gave them access to IBM Licensed Program Products (LPPs) with very attractive discounts. IBM provides special programs and incentives for developers to write applications for IBM i.
Even so, there are 2 key factors developers need to remember:
- This developer’s server cannot be used for productive use. (This means for software development, not for hosting customer applications.)
- The software keys must be renewed every 2 years.(They are not permanent)
When I helped the client upgrade their POWER6 to a POWER8, I was unaware that this server was originally a development server. The client also forgot and had been using it for hosting customers. YIKES.
After we transferred their IBM LLPs to the POWER8 and prepared to go into production, the client notified me that software keys had a 2 year term. They were alarmed because they had expected permanent software keys.
I had never seen this situation before. My IBM distributor had not seen it either.
So it took us several days working with IBM to come up with a fix. It took close to a month to fix it.
First, all the LPPs had to be relicensed (repurchased) as permanent software keys and uninstall the developer LPPs. (Unplanned costs – ugh!)
Second, the entitlements – IBM i core activation and user count – was much trickier. Even though the client had “bought” them at IBM list, they had been coded for a “development machine.”
My simple mind thought the IBM Key Center could manually change the code to make it permanent. Not so. I was dead wrong.
We had to credit the original IBM entitlements and re-order the IBM entitlements with permanent software key status.
Conceptually, this sounds simple. In fact, it took us about a month. My sense for the delay is all parties in the fix were not familiar with these steps needed to credit and re-order. (When have you ever received a credit for IBM i entitlements? It is a very rare transaction. And, my first.)
I also had several baffling moments.
I spoke several times to IBM Key Center to resolve the issue on behalf of my client. IBM Key Center told me that there was confusion with the machine and serial number involved – seems IBM Key Center was aware of 3 like servers with the same serial number – 2 servers were in France and 1 in Houston, Texas. While I explained the server in Houston was my primary concern, that there were 2 other servers added to the confusion and delay.
In the end, I am grateful for the help from IBM Key Center to get all squared away.
Now when faced with new servers, I am on the hunt for IBM software coded for “development” to avoid this kind of headache.
POWER5 User At V5R4 Upgrades To Used POWER6 At V5R4 Encounters Unforeseen Delays
Many IBM users remain on back-level OS versions because they no longer pay for their software developer’s support.
In this case, a 9406-520 user runs JD Edwards at V5R4. They had stopped paying JDE for support for many years so they chose to remain at V5R4.
Desiring more performance, this user purchased a used POWER6 entitled at V5R4 with unlimited users. They also bought IBM software support for the POWER6 so they could get software keys when they transferred their IBM LPPs.
On the surface, looks pretty straight-forward.
Not so fast.
First, IBM must update their records that this POWER6 has a “new” owner.
Second, the POWER6 configuration has to be updated in the IBM records – accurately. This took us about a month. Why? The used computer dealer radically altered the original configuration to satisfy the new user. It took us several iterations working with used computer dealer and IBM to get it straight.
(In this case, the used computer dealer did not understand what was needed to get it right in the first place. How many used computer dealers do you know that understand software keys, IBM I version levels and software version levels? I don’t know of any.)
Now, it gets even trickier.
Even though the 9406-520 user runs their JDE on V5R4, many years ago they had requested an IBM upgrade to V6R1 — that never happened.
When we submitted the request to transfer the IBM LPPs to the POWER6 at V5R4, I was told IBM only permits LPPs to be transferred to same or higher OS levels.
So we could not transfer LLPs at V6R1 to a server registered at V5R4.
The 9406-520 user freaked out.
He had just bought a POWER6 server and thought he could not get software keys at V5R4.
IBM Key Center explained the fix to me:
- Upgrade the POWER6 to V7R1,
- Transfer the LPPs from the POWER5 at V6R1 to the POWER6 (you can transfer LPPs to a higher OS level),
- Upgrade the LPPs to V7R1, and
- When all software is at V7R1, request from the IBM Key Center back-level software keys for V5R4.
Wow! I had forgotten you can get back-level software keys for higher OS levels.
Here’s why permits back-level software keys.
Many IBM i users run servers with multiple LPARs at different OS levels. So, IBM makes back-level software keys back to V5R2 available.
Without IBM Key Center help, we would not have figured that out.
So, the POWER6 user can run his JDE at V5R4 after all. Great news!
Conclusion
Navigating IBM software, entitlements and keys can be tricky. Pick a Business Partner with the experience to make it easier. Pick an IBM Business Partner with the tenacity and creativity to discover the solution you need.
If you plan a trip through the jungle, get a guide. If you get lost in the jungle, search the web for a guide to get you home safely.
Leave a Reply