×
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.
Chuck, I probably know more than enough to be dangerous. When working at
the Data Performance lab a couple years ago, we regularly mucked about with
LPARs. Learned it all the hard way, as Al says he did.
I'm going to say, it wasn't all that hard, in a way. But I wouldn't hire me
right now to set up a critical production system. We could afford to mess
up a lab system - that was part of our job - I even found a boundary
condition that caused an LPAR to refuse to start.
So, plan-plan-plan. Know what resources you will have - DASD, memory,
processors, other hardware. You need a load source for each partition,
IIRC.You probably need various separate towers for dedicated peripherals.
And save-save-save. I may end up doing an extra partition here sometime,
but I'll be sure I can recover from a gaff.
So, get some school or get some help. And try to watch someone, of you hire
it out - once set up, you can probably manage the config on your own pretty
easily.
Good luck
Vern
At 02:10 PM 3/17/2003 -0500, you wrote:
Hi Folks,
I'm not sure I know much more about LPAR than to be dangerous and we are
looking to upgrade a 620 to an 810 with LPAR. Should I be looking at
attending an LPAR class in Rochester ?
Thanks !
Chuck
As an Amazon Associate we earn from qualifying purchases.
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.