The hen it’s not your problem. You’ll just have to live with the messages. Alternatively you can write a message queue handler that will remove those messages if you really need them gone for audit or other purposes.


Jim Oberholtzer
Agile Technology Architects
Office: 414-433-4363
Mobile: 414-915-1445
Sent from mobile device

On Dec 27, 2023, at 10:03 AM, mlazarus <mlazarus@xxxxxxxxxxxx> wrote:

Rob,

It is somewhat confusing, especially since I haven't done heavy duty system operations in a while. Thanks for the explanations. This machine is being managed by a 3rd party, and I don't even have access to the HMC.

-mark

On 12/27/2023 10:05 AM, Rob Berendt wrote:
In the image I posted what was the sum? And the "Usage limit" in each
individual partition is also a sum and it needs to be greater or equal to
the sum shown in that image.
I think Jim did a pretty good job explaining it also.
What really gets fun is when you break the processors up into different
processor pools. I only do this for some products licensing requirements.
Let's say you're running some H/A vendors products on two of your 6 lpars.
Then you might put those lpars into their own processor pool or the vendor
may charge you for lpars you aren't even running it on. The theory being
that if they are in the same pool and you have some certain performance
adjusting on then it could borrow processor from the other lpars. I try to
see the other guys argument, even if it angers me.
However processor pools have zero effect on your original licensing
message. If that confused you, I apologize.

On Wed, Dec 27, 2023 at 9:22 AM mlazarus<mlazarus@xxxxxxxxxxxx> wrote:


Thanks Rob. Is this msg based on licensing for each individual
partition or the base/host license?

On 12/27/2023 7:22 AM, Rob Berendt wrote:

Assuming this is an HMC managed system, the sum of all the processors as
shown at https://imgur.com/310Rkvq needs to be less than that shown
WRKLICINF for that product. Sample:
Display License Information

Product ID . . . . . . . . : 5770SS1
License term . . . . . . . : V7
Feature . . . . . . . . . . : 5051
Description . . . . . . . . : IBM i

Compliance type . . . . . . : *KEYED
Usage type . . . . . . . . : *PROCESSOR

Usage limit . . . . . . . . : 12
Last update . . . . . . . . : 03/17/23 10:37:41

Threshold . . . . . . . . . : 10

On Tue, Dec 26, 2023 at 4:09 PM mlazarus<mlazarus@xxxxxxxxxxxx> wrote:



I noticed this msg on a fairly new partition on customer's box.

Message ID . . . . . . : CPF9E7F
Date sent . . . . . . : 12/26/23 Time sent . . . . . . :
15:40:47

Message . . . . : IBM i usage limit exceeded - operator action

required.

Cause . . . . . : The processor usage limit of 4 processors for

product

5770SS1, license term V7, feature 5051 has been exceeded.
-- Current processor usage across all active IBM i partitions is
16.00.
-- Current processor usage for the local partition is 1.00.

What does is mean? Is it a configuration or a licensing issue or

both?

-mark


--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.