× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



More important than the license exception message is IBM i will report that
to IBM who will in turn send you a full price invoice with no negotiation to
follow. That will be expensive.

Best to do as Roberto suggests, use a shared processor pool with one core in
it and use that for all your IBM i partitions.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Roberto José Etcheverry Romero
Sent: Wednesday, November 12, 2014 11:13 AM
To: Midrange Systems Technical Discussion
Subject: Re: Core licensing per LPAR or per machine?

The system accounts for each IBM i activation. You may assign 1 core to each
partition, but the system will start screaming bloody murder and saying
"total Core usage is over licensed amount". So, if you have 3 LPARs you can
assign cores but only up to 1 in total (you may create a processor pool and
inside that pool set them to unlimited so as to allow all LPARs to use 1
core in total IF the others aren't using it).
If you wanted to use 1 full core per LPAR you need 3 IBM i core licenses.

Best Regards,

Roberto

On Wed, Nov 12, 2014 at 2:05 PM, e-mail s44b1443 <s44b1443@xxxxxxxxxxxx>
wrote:

Thanks for the reply....I'm still a little unclear. I have all 6 cores
activated just not licensed for IBM i. I thought the key to license
(unlock) each core for IBM i was entered into the partition, if that
is the case what stops me using IBM i on any of the remaining
activated cores or is the key for IBM i directly related to a specific
core i.e. core 1 in my case?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


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



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.