Migration Survey Badly Needed!!!....I know I have posted this a couple
of times on the HP3K newsgroup but with no results. Hope someone can
have some thoughts to take it up with Interex..

One thing which needs to be included is to check with customer if they
have considered to re-engineer the entire set up Legacy Applications
to Open Systems - COM, EJB, etc and this does require a lot of effort.

Most of the tools I have gone through in HP White Papers are specially
focused on Very specifics like Image to Eloquence/Oracle or VPLUS to
VB or VPLUS to Web Interface, COBOL to ACUCOBOL, PERCOBOL, etc

I would like to propose my customer to have a framework where by
phasewise re-engineering of the Legacy application can be done
with/without using tools to Open Systems... I would also like to
identify which Components can be exposed as Web Services...

Now here I am not talking about just HP3000 but it will start first
with HP3000 and then parallely move AS/400, Mainframes etc application
which are more or less similar to the n-Tier Architecture..

Has anyone tried this ? I guess Rather than go for Big Bang
re-engineering I am proposing breaking down the legacy to Subsystems,
change GUI First since Legacy Applications are Tightly coupled and
then move one subsystem at a time!!! Bot the new and existing
remaining legacy should coexist till the legacy is phased out!

Any other better solutions / approaches ? If tools have to be used -
which ones ? In what Phase ? Why ? and What will I accomplish using
that tool to go where I want to go ?

Rather than have multiple similar systems requiring huge maintenance,
I would like to Propose One unified system with may components as web
services that can do much things automatically with partners.. I am
also open to other solutions i.e J2EE, .NET, etc.

Roshan Shah
Cross Posting from http://groups.yahoo.com/group/3kmigration

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *