×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Nathan, you have to know what you’re trying to accomplish before you can begin a project. “Modernization” isn’t something you can accomplish because it has no clear definition. The goal needs to be clearly defined and something that can be measured. In your example, the problem is aesthetics, and the perception of 5250 being outdated. The goal would be to eliminate that problem, most likely by moving to a web UI.
I’m all for letting 5250 go the way of the vacuum tube and the rotary phone. You just really need a clear goal that you’re trying to accomplish.
You accidentally clipped my quote, so here it is again:
“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)?”
Thanks
-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Friday, April 05, 2019 3:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: 5250 to Web Interface / Application Modernization
What's the business case for the modernization?
What's the budget (in time, labor & cash)?
I think at some point the only alternative to "modernization" is "migration" to a different platform, which some people promote under the guise of modernization. It's not a case of "if", but rather a case of "when". Organizations will only put up for so long with a signon screen that says "(C) COPYRIGHT IBM CORP. 1980". On the surface and underneath is an interface, architecture, and code that is horribly outdated, which becomes less and less maintainable/sustainable every year.
midrange.com
