Re: Processor shifting due to Mimix -- MIDRANGE-L

× 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.

Rob, I'm looking at doing something with Workload Capping Groups. Essentially "restricting" the mimix product to use "x" number of processors on a particular LPAR. The way it stands now it(licensing) looks at all LPARs on a frame using the product. I'm not sure that it will work but am pursuing.

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzaks/rzaksworkloadcapping.htm
--
Bryan

On Jul 19, 2016, at 9:38 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

resending with a subject line...

I have one Power 8 processors configured this way:
LPAR Assigned
VIOS11 0.25 DefaultPool (0)
VIOS12 0.25 DefaultPool (0)
RACK1HST 2.00 IBMiAppServer (2)
GDWEB 1.00 IBMi (1)
GDIHQ 5.00 IBMi (1)
GDISYS 1.00 IBMi (1)
MAIL1 3.00 IBMiAppServer (2)
TSM(AIX) 1.00 DefaultPool (0)

Due to Mimix license issues:
CPF9E72 - Usage limit of 6 exceeded. Grace period expires in 358 days on
06/12/17.
A user was added, but the usage limit for product 7VSI001, license term
feature 5002, was exceeded.
WRKLICINF
Product ID . . . . . . . . : 7VSI001
License term . . . . . . . : V6R0
Feature . . . . . . . . . . : 5002
Usage limit . . . . . . . . : 6
Usage Count Information:
All partitions . . . . . : 7.00

I need to perform some sort of action. Possible choices are:
- Pony up more money for Mimix.
- Move GDWEB out of the IBMi shared processor pool.
- Move GDIHQ and GDISYS (Mimix lpars) into a Mimix shared processor pool.

Comments? I'm leaning towards evicting GDWEB as I could find some time to

do that with minimal disruption.
--

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.