RE: ##EMailNumber 01-WNY-3818153 CISC to RISC - Transition of Several AS/400(s),

There are no real issues about connectivity between CISC and RISC.  It
is a different processor architecture not really a different operating
system.  Added features but the core concepts and connectivity is the
same.  The major thing to consider is if you have a mix of RISC and CISC
machines is compiling code on one or the other and ensuring that all
code is observable.  The number of applications that I have seen that
won't convert when going from CISC to RISC because of observability
problems is frightening.  It highlights the fact that you should have
up-tp-date source, a good change management system, and strong controls
over your production environments.

                                                James Turnbull
                                                AS/Tech Consulting

> -----Original Message-----
> From: Gordon Searles [SMTP:gsearles@blarg.net]
> Sent: Thursday, 2 October 1997 1:26
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: ##EMailNumber 01-WNY-3818153 CISC to RISC -
> Transition of Several  AS/400(s),
> 
> > 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.
> 
> 
+---
| 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
+---