• Subject: Re: Sys/36 virtual machine, or OS/400?
  • From: nina jones <ddi@xxxxxxxxxxxxxxxxx>
  • Date: Thu, 06 Jan 2000 19:26:31 -0600
  • Organization: Data Design Inc. http://www.datadesigninc.com

> Hi, I can't think any reason to go to s36E.  If you want to migrate, do it
> directly to native.  If you need data from/to the M36, you can use DDM
> through the ilan.


i don't know about that.  i think it depends on the situation.  

when the as/400 first came out, that was all there was.  there was/is a
migration aid that does a good job of analysing the information on the
36, setting up the information for the conversion, and then compiling it
on the as/400.  you go in and subtype everything and away it went.

it even recreated the objects for the dfu's

that would be the way i'd go if:

you had the source code.
you knew the source code was clean and matched the objects.  
you didn't have any unsupported features, such as wsu. 

i know it's sometimes tramatic for users to get used to a new system,
but i never saw any that had trouble after the first few days.  i
remember when we switched our own payroll service stuff over, the first
day the girl was throwing things in frustration over the differences in
the spool files and message handling, but by the end of the week, you'd
have thought the whole idea to switch it over was hers.

nj
+---
| 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 thread ...

Replies:

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