|
I think that it depends on waht the configuration of the shared prc. pool
is. If you put the 4 LPAR's in a pool with MAX 16 prc, and when each of the
4 LPAR scales beyond 1 CPU then I think that with WRKLICINF you will see 16
prc. usage across all 4 LPAR's in that pool.
On Mon, Dec 16, 2013 at 6:32 PM, Roberto José Etcheverry Romero <
tsetso.marinov@xxxxxxxxx> wrote:
On the same topic, i was wondering if 4 IBM i partitions with 1 cpulicenses.
assigned each but 4 virtual cpus and uncapped weights would count as 4
procs or 16...
On Mon, Dec 16, 2013 at 12:44 PM, Tsvetan Marinov
<tsetso.marinov@xxxxxxxxx>wrote:
Hi all,
I have very strange issue here and I blame the OS API but just in case
maybe someone has encountered the same issue.
So i have 7 V6R1 LPAR's on 9117-MMC P7 which are in a separate shared
processor pool with max 4 prc. limit to this pool and 4 prc OS
ofWRKLICINF for 5761SS!/V6/5051 shows that the usage limit is 4 but theusage
count accross all LPAR's is 16 which is not possible for sure because
thinksthe limitation of the shared pool.
I get CPF9E7F every hour and I'm getting anoyed since my customer
productthat this is a BIG issue, which is not :required.
Message ID . . . . . . : CPF9E7F Severity . . . . . . . : 40
Message type . . . . . : Information
Date sent . . . . . . : Time sent . . . . . . :
Message . . . . : i5/OS usage limit exceeded - operator action
Cause . . . . . : The processor usage limit of 4 processors for
it5761SS1, license term V6, feature 5051 has been exceeded.4,00.
-- Current processor usage across all active i5/OS partitions is
-- Current processor usage for the local partition is 1,00.
I checked 100 times that the LPAR is in the correct pool but even then
listshows the wrong usage across all the LPAR's.list
My system is with firmware AM740_100.
I assume that API QSYS/QLZARCAPI is bugged but I can't be sure.
Any clues, PTF or some trick?
Best Regards,
Tsetso
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: tsetso.marinov@xxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: tsetso.marinov@xxxxxxxxx
Before posting, please take a moment to review the archives
at http://lists.midrange.com/mailman/listinfo/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: tsetso.marinov@xxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: tsetso.marinov@xxxxxxxxx
Before posting, please take a moment to review the archives
at http://lists.midrange.com/mailman/listinfo/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: tsetso.marinov@xxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: tsetso.marinov@xxxxxxxxx
Before posting, please take a moment to review the archives
at http://lists.midrange.com/mailman/listinfo/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.