|
And a good reason to use IBM's LPAR validation tool.
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
Glenn Ericson <Glenn-Ericson@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/18/2003 11:17 AM
Please respond to Midrange Systems Technical Discussion
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>, "'midrange-l@xxxxxxxxxxxx'"
<midrange-l@xxxxxxxxxxxx>
cc:
Fax to:
Subject: Re: LPAR Classes ?
Just screwing around is not a good thing with cards and resources. You
have to follow the rules or expect intermittent failures or less than
optimum performance from your new system throughout it tenure.
At 10:47 AM 3/18/2003 -0500, Urbanek, Marty wrote:
>I have to agree with Vern.
>
>"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"
>
>We had IBM contracted to come out and set up a small 820 with 4 LPARs,
but
>due to our bureaucracy the machine showed up but the consulting contract
was
>not approved.
>
>As the days went by, I finally just started hammering at it myself. It
took
>a lot of trial and error, and I had to move a few cards around so each
>partition had enough hardware to boot. As I recall, getting certain
things
>wrong (bus and IOP assignments) meant that I had to blow away all the
>partitions and start over.
>
>Probably took me the better part of a week to set up all the LPARs
correctly
>and install all the OS/400s.
>
>I beat the bean counters by a couple of weeks, compared to waiting for
their
>signatures. Then I just had IBM check over what I did for an hour or two
and
>give it an unofficial blessing.
>
>If you have the luxury of having a "lab" type environment then I would
say
>the class may not be necessary, depending on your tolerance for
>experimentation, but if you have a tight schedule and have to get it
right
>on the first try, then I recommend the class.
>
>-Marty
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
>To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>or email: MIDRANGE-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.