Re: V4R4 and V4R1 interoperability

[dhandy@xxxxxxxxxxx (Douglas Handy)]

Nina,

> i heard that there were some problems with that approach, so
>we've been a bit leary of upgrading.  

One obvious (potential) problem is that V3R7 has language enhancements
over V3R2, so compiling with TGTRLS(V3R2M0) means you can't use any of
the stuff introduced in V3R7 like floating point, %edic() and other
useful BIFs, pointer math, *VarSize, etc.

But if you are using the same code base with your V3R2 clients, then
it is not an issue since you already restrict your coding style.

FWIW, just a few days ago I restored objects created on a V4R2 machine
compiled with TGTRLS(V3R2) to a V3R7 machine and didn't have any
problems.  It *may* be that observability is required -- I seem to
recall that it ran object conversion on the programs, although that
ran at sub-second speed per program so I think it was only resetting a
flag in the object description.

The same SAVF restored to a V3R2 system also worked fine, but the
restore time was horrendous due to the object conversion.

Doug
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---