Re: upgrade

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Pete,

I have 18 pmr's opened, or that have been closed within the last 28 days,
with V5R1.  If I was still running V4R5 or earlier on any of my machines I
can guarantee you that I would have pmr's on those releases in that same
status.  Would that stop you from upgrading to any of those releases?

It is great to have a machine, or an LPAR box to test new releases on.
This is our pattern:
170 first.  Dedicated to just the boss, runs Domino and some system
management.  Soon to be greenstreaked to a 270.
Development 820 next.  Used by the systems department.  Also used for
training.  Runs all of our applications in test mode, Domino, etc.
Backup 270 next.  This is our hot swap backup for Domino.  Domino has
built in clustering and you do not need a Mimix like product for Domino.
840 and web 270 last.  The 840 runs all of our applications live:  BPCS,
Software Plus, Peregrine EDI, Domino, Tivoli Storage Manager, several
Netfinity Servers, etc. The web 270 is a bumblebee dedicated to serving
www.dekko.com via Domino.

We will be putting 520 on the 840 and the last 270 on 9/20/2002.  We have
a scheduled downtime every 8 weeks and that is the next scheduled one.

While test machines are nice, having others test for you, like IBM does
with the early ship program, can be very useful.  But that is probably
your point Pete.  The questions are:
How many machines do you need others to test to give you a representative
sample?
Keeping in mind that new APARs are generated daily for existing versions
of the OS, are you going to freak if 1, 2, 3 or how many problems with
V5R2 are discovered after GA?  Or does the number not matter - you're just
saying that IBM will resolve this first flood after GA with the first or
second cume CDs?

If everyone waits until the first or second cume after GA before going to
the release, then is that theory valid anymore?  Or will it keep pushing
back until the nth cume CD?

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Pete Massiello <pmassiello@os-solutions.com>
Sent by: midrange-l-admin@midrange.com
08/27/2002 09:29 AM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: upgrade


Rob,

    While you and Bryan point out that there is a Cum out, don't you
think as more and more people start to use V5R2, more problems will
surface.  I am not saying its buggy, its just a fact of life as more
people use it, in ways and combinations that were not thought of, things
happen.

    As one of my former bosses used to say, I don't want all the arrows
in my back, I will wait a little.


    This is why its great to be able to have a  machine or an LPAR box
where you can "test drive" the software for yourself before you install
it on your Production box.

    Thats just my opinion.

    Pete

rob@dekko.com wrote:

>This is a multipart message in MIME format.
>--
>[ Picked text/plain from multipart/alternative ]
>Sorry, I really must remember to read all my email before replying.
>
>Rob Berendt
>--
>"They that can give up essential liberty to obtain a little temporary
>safety deserve neither liberty nor safety."
>Benjamin Franklin
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.