[continued from previous message]   
      
   changes: the hardware and host OS, but also the application code   
   itself, the user interface, database, etc.  I suspect that if it   
   were feasible to just lift the code and data off of the   
   mainframe and plop it onto something else, most would work just   
   fine.  But that's essentially never what happens.  The mainframe   
   is, at this point, so alien in the larger scheme of things that   
   it's impossible to "just" move with a recompile.   
      
   OTOH, I suspect that for _many_ projects if you were running on,   
   say, Solaris, it's pretty straight-forward to recompile for   
   Linux and run with more or less the same stack.  Of course there   
   is a lot of heavy lifting one must do in terms of testing and   
   qualification, but that is qualitatively different than having   
   no choice other than rewriting everything from the ground up.   
      
   >BTW, what is the general replacement for CICS transaction processing and   
   >how does the replacement functionality compare to CICS ?   
      
   This is outside of my wheelhouse, but back in the day things   
   like BEA Tuxedo could do this and more.   
      
   >> As for the cloud, the number of organizations moving back   
   >> on-prem for very good reasons shouldn't be discounted.   
   >   
   >Yes, and I hope the latest batch of critical system movers do not   
   >repeat those same mistakes.   
      
   I'm not sure what mistakes you're referring to, but let's hope   
   that system maintainers make fewer mistakes generally.  :-D   
      
   	- Dan C.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)