Hi folks,

we're on the way to move from mainframe (OS/390) to WinNT 4.0, UDB. We've
tested our system with UDB 5.2,
so far so good, it works.
But now we should upgrade our testing-system, before we are in production,
because now (and only now) there are no data on the productionserver. So the
upgrade would be easier.
Our choice was (is) UDB 6.1.
Now the question:
In a couple of threads before, I always read "take UDB V7.x instead of UDB
V6.x". Is there a reason,
why I should avoid V6.1? Any known problems?
My problem is: UDB V7.x is to new, and we've got no time to wait. And UDB
5.2 goes out of support.

Any help would be very appreciated,
Peter

I'm kind of wondering why you'd downgrade your operations so much by moving
from a mainframe to a microcomputer.  I suppose you could expect to save
money on DB2 Connect costs, but the reliability factor has to come in here
somewhere.

Actually, what I've read here is "UDB v7.1 with fixpak 2 (due out before the
end of the year) over UDB v6.1."  If you can wait until December, that's
probably sage advice for a number of reasons:

* DB2 v6 will go out of service before DB2 v7.
* You will have one less version of DB2 to purchase, saving money over the
long term.
* You will be able to take advantage of v7 functionality earlier, possibly
saving money in your own development costs.
* DB2 v7 has all of the fixes that DB2 v6 has, plus new functionality.

If you can't wait for v7.1 FP2, the consensus in this newsgroup seems to have
been "DB2 UDB v6.1 plus FP5".  That said, I, personally, have no opinion on
this.  I'm just trying to concentrate the combined postings I've read here.

Hi Darin,
thanks for your reply.
Well, the reason is: Our system resides on the mainframe of a computing
centre of an other
company. Unfortunately this computing centre moves from mainframe to SAP R3
and shuts
down the mainframe. So we have to move to a system which we are able to
manage, because
we don't want to search for an other computing centre.

Peter