Re: Problems transferring with i Nav between V7R1 and V5R4 -- MIDRANGE-L

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

Thanks for those PTFs, Evan. They'll be handy when I get further down the road. But for now I'm just trying to send a test library with just a single source file. That's still bombing.

Joe

What kind of objects are you trying to move ? There are PTFs required
to allow programs to be restored from V6R1/V7R1 back to V5* releases:

V5R3M0 = MF41354
V5R3M5 = MF41734
V5R4M0 = MF40520
V5R4M5 = MF42655

On Thu, Jan 13, 2011 at 9:37 AM, Joe Pluta<joepluta@xxxxxxxxxxxxxxxxx> wrote:

After upgrading to V7R1 of iNav, I unhappily report the same result. I
can move objects from the V5R4 machine to the V7R1 machine, but not the
other way. On the V5R4 machine I see a QHST log entry saying that the
unpack failed because of incompatible SAVF release.

Reminds me of the way we could move data from the S/38 to the AS/400 but
not vice versa when we were converting BPCS to the AS/400. Chuck Myaard
said we would have to "wumpus up a way" to move the data, and we did -
and the WRKWUMPUS command was born. :)

Joe

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.