Re: Reasons to Upgrade to V6R1

Don't know if it is as simple as that. Observability on applications is the
big problem. We have at least one application that we do not have source, no
vendor anymore and still be used plus we have to a bunch of others that need
to be upgraded to get the observability before they can consider upgrading.
Operations says they are struggling with this one. I really want V6R1 but a
lot of work to get there.

On Fri, May 8, 2009 at 11:37 AM, Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx

wrote:

On Fri, May 8, 2009 at 16:39, Salter, James <JSalter@xxxxxxxxxx> wrote:

I am putting together a document on why we should upgrade to V6R1.

Can anyone list some good reasons to upgrade to V6R1 from V5R4?

Support for V5R4 will be dropped at some point. Staying on V5R4 and
making a direct jump to V6R2 will not make your life easier.

Upgrading the OS release isn't much work - just ensure that all the
vendor software you have supports V6R1, install the OS upgrade, check
that everything works, done. No need to make a big deal out of this.

If you have higher availability requirements (for example, you can't
afford 16h downtime on a weekend), then you can just run on your
second machine during that time, and switch back to the primary one
after the upgrade. :)

--
Read my blog at http://projectdream.org
--
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.