RE: 5250 to Web Interface / Application Modernization

Excellent. Knowing where you're going and why will help you get there.

My company is firmly in the "5250 or die" camp, so we haven't done any large moves. I use RPG/CGI for a number of critical webservices (and about a dozen skunkworks interactive apps).

If you're looking at doing an en masse move in a relatively short timeframe, you'll almost certainly want a commercial solution of some kind. If a slower pace is desired, a DIY approach would work. In that case, I think the question you have to ask is, "PHP? If not, then why not PHP?".


Good luck,




-----Original Message-----
From: Kirk Yates [mailto:kirk.yates@xxxxxxx]
Sent: Monday, April 08, 2019 8:42 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: 5250 to Web Interface / Application Modernization

Reply: Friday, April 5, 2019, 12:06:33 PM

1) Move to web interface. Get rid of the perception on the antiquated system, and add additional functionality.

2) Budget - we're collecting information on various options and what they would cost in time, labor, and cash.

What's the business case for the modernization? Is it
aesthetics/perception? Are you looking to extend the reach of your
apps? Need to add functionality that's impractical for 5250?

What's the budget (in time, labor & cash)?

--
Kirk Yates