Actually, the way I was looking at it was that as soon as you combined the two worlds, zLinux and zOS, under a single zVM, you'd incur the additional software cost in zOS because of the engines zLinux used.
If you brought up zVM in an LPAR for use as a test bed for zOS, then unless you added an engine for this purpose, you wouldn't increase your software licensing costs. But if you added additional workload to zVM that required additional CPUs to be added (such as adding zLinux guests), then your zOS software licensing costs would go up, even though zOS wasn't getting any benefit from the additional CPUs. That's why isolating the zLinux workload into IFL processors makes so much sense. -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Thursday, September 01, 2005 9:44 AM To: [email protected] Subject: Re: IFL engine for z/VM In addition to z/VM on IFLs for Linux, z/VM in a standard engine LPAR can provide a low-cost, on-demand test bed for VSE, z/OS, and TPF installations as well. Yes, you will have to pay for z/VM on your standard engines, too, but it may be more cost effective in some cases than using LPARs. To be clear, adding z/VM to the standard engine (CP) side of your box will not increase your z/OS software costs. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
