Re: Licensing on LPAR's

Did you reply to the right email?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of a4g
atl
Sent: Thursday, March 31, 2022 2:07 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Licensing on LPAR's

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


It is something I cannot argue against.
PTF's have not been installed since 2017. Applying all at once is a threat
management refuses to take. Once we have a DR site established, we can try
to install PTF's again.
Darryl.

On Fri, Nov 12, 2021 at 11:07 AM Rob Berendt <rob@xxxxxxxxx> wrote:

<snip>
Is it licensed to the serial number?
</snip>
Depends on what you mean by "it". Generally OS products are licensed to
the serial number.
Now, if you have a mix of IBM i, vios, aix, linux, then there are
considerations like you do not have to license IBMi for the total
processors in the machine, just to those processors consumed by IBMi.

Not only is there IBM to consider but there are vendor packages.

Some are licensed to the lpar number also. See the "PARTITION ID" below.

Some, HelpSystems for example, seem to find every possible thing they can
charge you for. Number of processors, number of processors licensed for
IBMi, number of processors in the lpar's shared processor pool, ...
Have one of their products on one lpar but not on the other? Well you
better make sure they are in different shared processor pools or you're
paying for the processors consumed by both. I guess the argument is that
the using lpar could borrow processors from the other one(s). I have one
system carved up into multiple shared processor pools. One for the lpars
replicated by H/A software (licensed by that), one shared processor pool
for the lpar running GoAnywhere, one for other lpars using IBMi. Then
there's the AIX and vios...

See also:
CALL QLZARCAPI
Message ID . . . . . . : CPF9897
Message . . . . : PARTITION INFO -> NETWORK NAME: GDIHQ . PARTITION
NAME:
GDIHQ. PARTITION ID: 5. SHARING TYPE: SHARED. SHARING MODE: UNCAPPED.
MIN
PROCESSING CAPACITY: 2.00. DESIRED PROCESSING UNITS: 4.00. MAX
PROCESSING
CAPACITY: 6.00. ENTITLED PROCESSING CAPACITY: 4.00. MIN VIRTUAL
PROCESSORS:
2. DESIRED VIRTUAL PROCESSORS: 10. MAX VIRTUAL PROCESSORS: 12. ONLINE

VIRTUAL PROCESSORS: 10



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of

a4g

atl
Sent: Friday, November 12, 2021 10:45 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Licensing on LPAR's

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


Something I have never been concerned with until now.

How does IBM treat licensing on LPAR's?
For example: Is there a difference if there is 1 LPAR or 20 LPARs? Is it
licensed to the serial number?

Darryl Freinkel.
--
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.

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

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