Look at COBOL. How many jobs was California looking for a few years ago? I
thought COBOL was dead YEARS ago.

It is always the same arguments and same outcome. A slow decline, but never
dies.

--
Mike Wills
http://mikewills.me


On Wed, Mar 28, 2012 at 1:46 PM, Jerry Draper <midrangel@xxxxxxxxxxxxx>wrote:

How can executive management justify keeping iSeries systems when the
pool of RPG programmers are of retirement age or so?

Is that a myth promulgated by *IX PHP folk?

At one place I am hearing that one justification for moving off of an
iSeries is that no "younger" programmers are interested in learning RPG
or it derivitives (ie: RPGILE).

Anyone else encountered this argument?

My view is that RPGILE is just another coding system with a learnable
syntax and that much of the user experience is via front ends written in
java or .net.

The iSeries is a great db engine serving up data to whoever wants it (or
is authorized to it). Tried, true, and trustworthy.

If we are all going to retire at the same moment will the iSeries go poof?

Jerry



--
Jerome Draper, Trilobyte Software Systems, since 1976
iSeries, Network, and Connectivity Specialists -- iSeries, LAN/WAN/VPN
Representing WinTronix, Synapse, Netopia, HiT, and others .....
(415) 457-3431; www.trilosoft.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].