On Monday, 10/02/2006 at 04:29 AST, "Dodds, Jim" <[EMAIL PROTECTED]> 
wrote:
> Thanks Mark. I have found the answer on the MP3000 in the configuration
> section of my LPARs. The TECH LPAR is marked as LINUX only. My next
> question is I think that I still don't have an IFL. Can the general
> processor be shared between these 2 LPARs with the TECH LPAR marked as
> Linux only? What would happen if I changed the TECH LPAR from Linux only
> to ESA/390? Would that mean I would have to some changes to the Z/VM 4.4
> or would it IPL ok with no changes?

A "Linux only" CPU is an IFL (Integrated Facility for Linux).  An LPAR can 
only share CPUs with other LPARs that have the same type of CPU.  That is, 
you can only share your TECH CPU with another LPAR you have marked "Linux 
only".  Likewise for the standard ESA/390 CPU.

If you change the VM CPU to ESA/390, then you need to go back and check 
your various license charges.  Right now your VSE software is being charge 
according to the MSUs (sort of model group), and that number is based on 
the number of ESA/390 CPUs you have.

Also, your z/VM license is probably based on the number of IFLs because 
you have chosen to run it ONLY on IFLs.  If you change it to ESA/390, then 
you will have TWO CPUs worth of z/VM capacity and and you will owe IBM an 
additional z/VM processor license fee WITHOUT REGARD to the fact you have 
configured only a single CPU to the VM LPAR.

This is why IFLs were invented.  They allow the introduction of Linux 
workloads without increasing your ESA/390 (traditional) software costs.

If you want to use z/VM for non-Linux purposes (e.g. VSE DASD migrations), 
then you need to run a second copy of z/VM in a 3rd LPAR that is defined 
to share your PROD ESA/390 CPU.  Then you can run VSE as a guest, but you 
will still owe IBM an additional z/VM license fee.  (In this case your VSE 
software costs won't increase since the MSUs on the box won't change.)

So be sure to consult with your Purchasing and/or Legal departments to 
find out what you are licensed for, and keep the CPU configuration 
consistent with those licenses.

Alan Altmark
z/VM Development
IBM Endicott

Reply via email to