Not that likely that they would be doing 5250 development at that time but
using RPG for back-end "grunt" work for a different UI is still a very
good option and possibly however.
From: John Yeung <gallium.arsenide@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/06/2014 05:12 PM
Subject: Re: how to determine cost savings based on resource
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On Thu, Dec 4, 2014 at 4:48 PM, <Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx>
Also there is the future issue of the company having to replace me when
they kick me out of the door or I retire. Finding a qualified candidate
that knows and is willing to write, maintain "obsolete" methods of RPG
will be a nightmare if not impossible.
I don't share this view. RPG is just not that hard a language to
learn. It's not a mind-bending language. Honestly, any competent
programmer should be able to pick up enough RPG in a matter of weeks
(if not days) to be able to start productively contributing to
maintenance. It may take somewhat longer for them to become fluent
enough to write new code, particularly complex 5250 green screens.
(And how sad would it be if your company is still looking to develop
brand-new 5250 code when you retire?)