• Subject: Re: ##EMailNumber 01-WNY-3818153 CISC to RISC - Transition of Several AS/400(s),
  • From: "Al Barsa, Jr." <barsa2@xxxxxxx>
  • Date: Thu, 02 Oct 1997 09:11:29 -0400
  • In-Reply-To: <34326B96.477@blarg.net>

At 08:26 AM 10/1/97 -0700, you wrote:
>> I was told that I could run the CISC to RISC Migration in any of the AS/400
>> (s) at different times and not to worry about connectivity after
>> completion.
>I know that there is a section of the roadmap that covers connectivity
>in a mixed environment that is the place to get the definitive answer. 
>We have 4 AS/400s (3 production, 1 development) and we have migrated the
>3 production to RISC and will be migrating the development to RISC in
>November.  We have not had any problems with connectivity.  All that
>said your mileage may vary.            

Yes and no.  Assuming you want to save/restore objects from RISC to CISC,
you have to live within the rules of what S/R supports.  In other words,
the oldest CISC release that you can restore to from V4R1 is V3R1.  When we
get to the release after V4R1 (whatever it will be called), you can bet
that the oldest CISC release you can restore to will be V3R2.  It's likely
that V3R2 will be supported for some time, but don't count on it forever.


Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406

Private mail should be sent to barsa@ibm.net
| 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 MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].