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

Hi Booth,
I had done this several times, the creation of the m36 machine is really
easy and you don't have to stop the production system to create o delete
one, besides, it will be easy for your users to keep track of their
operations.  The learning curve is minimal for operators (I use to give a 30
hrs session including 15 hrs lab to have then starting, finishing and
managing the new environment, there are also some new procedures, and the
SSP include things like pop, wrkspl procedure and others) and none to end
users.  Users usually don't know if they are running an AS/400 or the s36
besides the speed. (Once, a user call us asking about when we where going to
start the migration two weeks after we where on the as/400). If you start
migrating to native, getting data to/from m36 environment is really easy
with ddm and ilan.  Even the file transfer for PC is really easy and faster,
you can start using CA/400 express or standard.  One other thing, the disk
limit for a M36 machine is an incredible 4GB(if I my memory serves well) vs.
the 1.2 GB limit you had before.

FWIK, this scheme is a win/win situation for your client.

P.D. One recommendation, get the dkt drive for the as/400, it would be easy
to save/restore data for the migration.  And, if your application use a lot
a copydkt, remember, there is no magazine drive for the as/400, and copying
from/to tape is a lot slower, we correct this using copyfile instead.

Emilio Padilla.

----- Original Message -----
From: <boothm@earth.goddard.edu>
To: <MIDRANGE-L@midrange.com>
Sent: Jueves 6 de Enero de 2000 10:57 AM
Subject: Re: Sys/36 virtual machine, or OS/400?


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