× 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.



We've already done the object analysis and gotten any source from our
vendors that is needed to recompile objects for 6.1. Like I said before,
we want to go there, we just have to fit it in with other priorities right
now.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/15/2010 06:11 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Bleeding edge Was: DDL Record Select






On Mon, Mar 15, 2010 at 13:55, Bryce Martin <BMartin@xxxxxxxxxxxx> wrote:
Just in case you missed the memo Lukas... is 6.1 not V6R1. 7.1 is in
beta.... V7R1 doesn't exist. Time to update your IBM Terminology
Database

As others have mentioned, i've seen V7R1 much more than 7.1 :)

We would love to go to 6.1 but we don't
have the time right now and honestly we wouldn't really be gaining a
whole
lot.

First off, you're on V5R4 and current on PTFs. That's a lot better
than many other shops i've seen.

But either way, you'll need to make plans. Plans, to upgrade to V6R1
or V7R1. In either case, object conversion is required. If you're
afraid of going to V6R1 because of that, you won't gain anything by
waiting.

Basically, it boils down to this - you can stay ahead of the curve,
and upgrade to new releases aggressively. That's what i'm doing on all
our internal systems. I'm doing this for several reasons - to gain
experience doing system upgrades on production systems, to make sure
that our software runs flawlessly on current OS versions and to
benefit from IBMs newest additions.

Doing this isn't for everyone - it makes sense for use since we're an
ISV, but if i was working on "just" one system for internal use, i
wouldn't be that agressive.

The next path is to upgrade as soon as it makes sense - for example,
upgrade to V6R1 after it was for 0.5 - 1 years, or as soon as support
by third party vendors permits.

Or one can stay on whatever release they are, because doing upgrades
might break something. This is usually a vicious cycle - you don't
install PTFs because they might break stuff, you don't upgrade the OS
because that might break stuff, and you don't upgrade third party
software because that might break stuff. And then, a few years later,
you need to upgrade because of business reason x (where x can be a new
feature requirement, or just the extremely expensive maintenance cost
of running a 720 on P20 with V5R2 instead of a 8304-E8A at P10).

And at that point, you need to upgrade everything, in one swoop.
You're not familiar with upgrades because you don't do them often.
You're not familiar enough with the software you use, because you
didn't do upgrades in the past.

I've seen the latter happen a dozen times. Not doing anything until
you really really really need to is not a good strategy.

Again: Running V5R4 with the latest PTFs isn't bad - you just need to
have a plan for going to V6R1 at some point.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.