Thanks to all for your input. I really appreciate it!
Take care,
Michael
From: David Boyes
To: LINUX-390@VM.MARIST.EDU
Sent: Monday, January 9, 2012 9:20 AM
Subject: Re: Question about zVM and MF configuration
> I have found myself having to defend the
n experienced VM system programmer there!'. It felt good. Ha ha ha.
Again THANKS A BUNCH
From: David Boyes
To: LINUX-390@VM.MARIST.EDU
Sent: Monday, January 9, 2012 9:20 AM
Subject: Re: Question about zVM and MF configuration
> I have found mysel
> I have found myself having to defend the way we are now configured vs. a
> co-worker who has come back from class saying his instructor said we should
> run 2 LPARs, one with zVM and zVSE and the other one house our production
> zLinux and DB2 images.
This sounds like a recommendation from the
Alan and Tom have very valid points.
Here's some more thoughts.
You may have security/audit reasons or management policy for not running test
and production on the same HW. (We don't even run them in the same state :)
You may also find that some production applications are much more sensitive
In my experience, it is Linux that interferes with zVSE , but that is
only in a scarce memory configuration.
Consider that zVSE workloads really don't change the amount of memory
needed, month to month.
However, add a Websphere Linux image (take any "large to you" linux
application), and add it to
On Wednesday, 01/04/2012 at 04:53 EST, Michael Simms
wrote:
> I have tried to explain how mainframe architecture and zVM have
> been designed as a sharing environment while at the same time protecting
> against influences from any given guest machine, should the
configuration be
> configured just
one lpar works well, shares storage, shares other resources, reduces
overhead, reduces system programming efforts, reduces costs. And I can
show other mixed mode LPARs with both VSE and linux in the same LPAR.
Was it a hardware vendor recommending increasing your hardware costs
Michael Sim
I hope everyone had a safe and happy one Holiday Season.
I need some guidance, advice and/or ammunition on an issue that has come up
regarding mainframe configuration.
I have found myself having to defend the way we are now configured vs. a
co-worker who has come back from
class saying his i
