Migration from Powerhouse MPE

[Roshan Shah]

Guy,

Thanks for the response. I am aware of the effort of
rewriting in 3GL. But the question is when the final
move to J2EE/.NET is decided after this interim urgent
migration need, what would be availability of
Powerhouse Resources and more importantly at what rate
? Even today, I find it difficult to locate these
resources and God knows what would happen then..

Well - Either today or maybe some years down the line
Powerhouse has to be replaced with Future State
Platform.. I feel that it would be a wise decision to
do it now...! Unplugging powerhouse means that We only
then have to deal with COBOL technology in future
reengineering.

Just few thoughts.. I'm sure others would have better
ideas!

Roshan Shah

--- Guy Werry <guy.werry@hbms.ca> wrote:
> Speaking STRICTLY for myself (not for my
> corporation!), I would question
> re-writing in a 3GL.
> Given the level of effort that's going to be
> required - on-line Cobol is no
> picnic, might you be better off going to another
> 4GL, like Powerbuilder, IF
> there's more of a talent pool out there?
> 
> You have to consider the productivity hit that
> you're going to take.  I have
> 22 years in the business, starting with Cobol and
> moving to Powerhouse.  I
> head the maintenance effort for all of our software,
> so we have Cobol,
> Fortran and Powerhouse.  I DO NOT write a report in
> the 3GLs, unless a Quiz
> report is impossible, because the productivity in
> Quiz is so much higher!
> So, if you re-write in Cobol to save license costs,
> you will be paying
> through the nose every time that you develop a
> report in Cobol - even with
> templates it will probably take you 2 to 3 times as
> long to develop the
> report - especially in the case of simpler reports.
> 
> Another possibility is internal training / career
> development.  If you have
> people who are half-way loyal, then training them in
> Powerhouse, even if it
> is just internal training can work pretty well. 
> Unfortunately, we don't
> know if your shop is relying on consultants for
> work.  If so, then the
> internal training idea may not be feasible.
> 
> 
> -----Original Message-----
> From: Roshan Shah [mailto:roshan_shah@yahoo.com]
> Sent: September 18, 2003 8:36 AM
> To: powerh-l@lists.swau.edu
> Subject: Migration from Powerhouse MPE
> 
> 
> Hello,
> 
> I wanted to have your inputs on strategy of doing
> Powerhouse Migration to Sun Solaris.
> 
> a) Migrate Powerhouse Application to Solaris.
> Powerhouse is available on Solaris
> 
> b) Rewrite Powerhouse to COBOL! (Licencing
> Powerhouse
> is very expensive)  - Should one at all have
> Powerhouse even if it is an interim solution looking
> into the fact that Powerhouse resources are scarce
> and
> fast depleting.
> 
> Also when in future if Powerhouse Resources are
> needed, they will not only be very expensive but
> very
> rare!
> 
> 
> Any other recommendations ?
> 
> Roshan Shah
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site
> design software
> http://sitebuilder.yahoo.com
> = = = = = = = = = = = = = = = = = = = = = = = = = =
> = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe <password>" in message
> body to
> powerh-l-request@lists.swau.edu
> http://lists.swau.edu/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you
> must be a subscriber.
> = = = = = = = = = = = = = = = = = = = = = = = = = =
> = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe <password>" in message
> body to powerh-l-request@lists.swau.edu
> http://lists.swau.edu/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you
> must be a subscriber.


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com