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



Rich Garcia wrote:
>You should really keep an AS400 system at V3r2 if you are at V4R1 and still
>have a mixed batch in the field, this will save you time. My company has
>200 plus AS400's and most are at V3r2 though some have just been upgraded
>to V4r1 Risc machines. The reason for keeping a system at V3r2 is that you
>will be unable to send objects from V4r1 to previous releases.

Are you saying there is no way to send objects from V4R1 back to
previous releases?  Even if the objects are created to prior release?

This is an important issue for us, as we are currently mirroring one
530 to another using Vision Solutions OMS Gold Suite.  We will be
upgrading both machines from V3R7 to V4R1 in the near future.  When we
upgrade, our plan is to upgrade the target machine first, so we will
be sending objects from V3R7 to V4R1.  Not a problem, I would imagine.
However, in a role swap situation, if we could not send objects from
V4R1 back to V3R7 we would want to be aware of this before we upgrade.

Terry Herrin
Sr. Programmer/Analyst
New Hanover Regional Medical Center

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.