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


  1.  Home
  2. MIDRANGE-L
  3. March 2011

Re: V5R4M5 to V6R1

That's not /entirely/ true. For example, as I've reported in a few posts SQL at 7.1 is a bit more restrictive than V5R4. Granted it's primarily when dealing with "malformed" data (also known as legacy data :) and the issues are pretty clearly documented in the memo to users, but it's not a 100% slam dunk.

Joe

Only one question: Why stop at V6R1? The jump to V7 from V6R1 is
almost nothing from an upgrade point of view, but you get quite a bit of
extra "stuff" at V7. The only reason not to go all the way is an OEM
vendor holding you back. (a good reason to look for a replacement in my
view)


Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 3/28/2011 1:50 PM, fbocch2595@xxxxxxx wrote:
Hi Folks, we're finally going to upgrade to V6R1...I haven't seen any problems when doing this upgrade for awhile. Anyone have any new stories to share regarding this upgrade or is there little to nothing to worry about when doing this upgrade?
Thanks, Frank


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.