Re: Sys/36 virtual machine, or OS/400?

Pat/Booth,

>you could then begin to migrate out of the S/36EE to full native... This
>method requires nothing more than a recompile...

Maybe, maybe not.  Restoring to the *M36 is a pretty fail-safe
operation since everything is guaranteed to work just as before, only
faster.  The *M36 is object code compatible with the S/36.

But moving to the S36EE is a migration process that may or may not be
smooth and easy, depending on the applications.

You need to have all the source, and you can't migrate stuff like WSU.
In addition, non-IBM assembler subroutines are not supported.  Plus if
the source used the RPG II 1/2 or RPG III like extensions available
from third parties like ASNA, then the source may be incompatible with
the RPG II compiler of the S36EE.

The S36EE does have stuff to help in recompiling and tracking the
results.  See the STRS36MGR command.

That being said, the S36EE has the advantage of better coexistence
with native applications (since they can share the same files), so it
is a much better place to be (IMHO) if that is where you are trying to
end up.  The *M36 is great for avoiding the migration process or if
you use WSU or assembler routines or don't have all the source, etc.

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