Re: Re[2]: Sys/36 virtual machine, or OS/400? -- MIDRANGE-L

Eric, thank you for those words; I feel a lot better.  I can see now that 
going directly to S36E would likely stop the business in some 
unpredictable way and that would be an awful black eye.  The Business 
Partner is being heads-up on this I bet.
_______________________
Booth Martin
boothm@earth.goddard.edu
http://www.spy.net/~booth
_______________________




eric.delong@pmsi-services.com
Sent by: owner-midrange-l@midrange.com
01/06/2000 01:51 PM
Please respond to MIDRANGE-L

 
        To:     <MIDRANGE-L@midrange.com>
        cc: 
        Subject:        Re[2]: Sys/36 virtual machine, or OS/400?


Well, don't give up hope yet. I think, depending on the time allotted to 
the 
switchover, you'd be just as well off running everything as is in the M36, 
and 
then start a project to migrate to S36E. Once you've converted and tested 
everything, the users can be switched over to the emulation environment 
and M36 
can be dumped. This way, there's no real downtime for the customer.

As far as migrating apps to the S36E, most of it is a piece of cake, 
usually. 
Most RPGII programs require minor changes to F specs (especially display 
files).
OCL generally runs fine without modification, though I recall there were a 
few 
issues with some of the commands. Sorry I can't remember more details. I 
remember most of the problems we had involved MRT programs and 
communications 
programs. Also be aware that WSU won't port, and DFUs must be rebuilt.

hth,
eric.delong@pmsi-services.com 

______________________________ Reply Separator 
_________________________________
Subject: Re: Sys/36 virtual machine, or OS/400? 
Author:  <MIDRANGE-L@midrange.com> at INET_WACO
Date:    1/6/00 11:57 AM


I have a real sinking feeling about this.  A business partner sold them 
this setup and is installing the M36, but the client is looking forward to 

gradually installing new OS/400 applications and features.  From what you 
are saying Eric, it sounds like that isn't going to happen?
 
How tough is it to migrate from the M36 to S36E?  Is it a data save and 
restore some day in the future?
_______________________
Booth Martin
boothm@earth.goddard.edu
http://www.spy.net/~booth
_______________________
 
 
 
 
eric.delong@pmsi-services.com
Sent by: owner-midrange-l@midrange.com 
01/06/2000 11:18 AM
Please respond to MIDRANGE-L
 
 
        To:     <MIDRANGE-L@midrange.com>
        cc: 
        Subject:        Re: Sys/36 virtual machine, or OS/400?
 
 
     Booth,
 
     Though I haven't ever work with M36 systems, my understanding is that 

 
     you'll end up with a SSP virtual machine running under OS400. M36 
runs 
     s36 objects just like a S36, no RPG3 or RPG4 in this invironment. New 

 
     apps in RPGIV can be developed on the OS400 side, but the cannot be 
     accessed directly from the M36 side. Data can be exchanged between 
the 
     two via DDM, but not directly as is possible in S36E (emulation 
     environment).
 
     If your client is planning to enhance applications via RPGIV, you may 

 
     want to use S36E instead of M36, because S36E can use a mix of RPGII, 

 
     RPGIII, RPGIV, OCL, CL, REXX, etc...... 
 
     If your client has S36 apps without source code that cannot be 
     upgraded, you're stuck with M36 as it is object compatible with the 
     S36.
 
     hth,
     eric.delong@pmsi-services.com
 
 
______________________________ Reply Separator 
_________________________________
Subject: Sys/36 virtual machine, or OS/400? 
Author:  <MIDRANGE-L@midrange.com> at INET_WACO 
Date:    1/6/00 10:20 AM
 
 
A client is switching to a new AS/400 from his Sys/36.  It is being 
installed in a M36 virtual machine.  Will that allow full OS/400 function, 

 
including RPGIV, for new development and applications?
 
 
_______________________
Booth Martin
boothm@earth.goddard.edu
http://www.spy.net/~booth
_______________________
 
+---
| 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 
+---
 
 
 
+---
| 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
+---
 
 
 
 
+---
| 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 
+---
 


+---
| 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
+---




+---
| 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
+---