In our case, where we literally unplugged the cable for the expansion unit drives from the P8 and plugged it into the P9 we were unable to enter reduction keys. We told IBM the situation and they understood. NBD.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Monday, May 6, 2019 3:38 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: Usage limit help (CPI9E19/CPF9E72)

Been there, done that.
We had a very similar issue.
The reduction keys were throwing an error, could not enter them.
On the old system, you also need reduce the virtual processor settings to 1 desired and 1 max before entering the reduction keys.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Monday, May 06, 2019 2:22 PM
To: Midrange Systems Technical Discussion
Subject: RE: Usage limit help (CPI9E19/CPF9E72)

OK. I've been the squeaky wheel, but I guess I need to squeak louder.

Thanks



-----Original Message-----
From: Jim Oberholtzer [mailto:midrangel@xxxxxxxxxxxxxxxxx]
Sent: Monday, May 06, 2019 9:35 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Usage limit help (CPI9E19/CPF9E72)

On and upgrade like you are describing, it's likely the key center is waiting on the reduction key data from the old system.

Check the keys (WRKLICINF) for 5770SS1 - 5050, 5051, and 5052. Those sound like the ones you are referring to.

The process to move software from one serial number to another is not complicated but detailed.
1) BP orders reduction keys for donor machine, Key center provides them.
They are good for a limited time
2) you enter the keys into the donor machine and get a series of screen shots that show the keys were entered. This effectively turns the donor machine into a vegetable. Instructions from the key center are precise, and easy.
3) Screenshots back to key center, they usually respond within about 24 hours with new permeant keys for the new serial numbers.

The fact that so many days has gone by without your capacity keys showing up suggests a foul up in the transfer. Assuming the donor machine is long gone or cannot be powered up because you moved parts to the new system, you'll have to provide proof the donor machine is no longer in production and not
being used. That can take many forms as requested by the Key Center.

The BP has to step up on this one.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Monday, May 06, 2019 9:23 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Usage limit help (CPI9E19/CPF9E72)

About 42 days ago, we upgraded from POWER7 to POWER9. Our business partner did the upgrade and provided a Word document with our new license keys (the IBMi commands). I copied-and-pasted the commands into a 5250 session to run them. The next work day we started noticing CPI9E19 and CPF9E72 "Usage limit" messages. Assuming it was related to a license key, I reentered all the license keys. That made no difference, so I installed them directly off IBM's website. Still no change.

Our business partner tells us every week that they're still waiting on IBM to get this resolved. The grace period is down to 28 days, and I'm starting to get nervous. How long does IBM normally take on these kinds of things?
Is this something I should take up directly with IBM?

I appreciate any thoughts/suggestions/advice.

Thanks


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.