Hypothetical question (yes, really hypothetical): At what point do you
decide to re-write a program rather than fix it? And, if the decision
is to re-write it, how do you justify the decision to TPTB?
Consider the following ... you have a program that's about 15 years old.
Written in RPG III, converted to ILE using CVTRPGSRC but never updated
to take advantage of ILE capabilities, and it's a total mess (by fairly
modern standards). Continued modification to the program just seems to
make it worse. The program is not small ... and fairly key to the
system you are working on.
How can you justify a re-write? How can you quantify the cost / benefit
ratio to show that a re-write would be in the best interests of
p.s. and, just in case someone from my employer is reading this message,
this is truly a hypothetical situation ... although we do have some
pretty old code.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.