If you have a good stable system, it will be very hard to justify modernizing (no changes, it just runs)
Risk is very "risky" to use, I think it is better "cost".
My experience has been to modernize each program that needed any changes, and sometimes other programs related. Now I just have just a few very old programs.

A good reason to modernize is to learn how the system works, and that will reduce cost in future maintanance. Make the system easier to audit will be a reason.

Just replacing old code for new code that does the same thing is bad businness (for the one that pays)
The modernized system must be better for the user. Faster, pretier, easier, give more info, etc.

John E wrote:

The "value proposition" would be to make the software "fit", i.e. (more)
easily adaptable to changing business requirements, and mitigate risks. But
this is not quantifiable.

So the key word is to reduce "risk", and risk is something companies don't
want, as it can cost dearly and unexpectedly.

But i don't know if it's a good idea to tell the boss that the current
system is "risky".

On Tue, Dec 2, 2014 at 11:58 PM, <Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx> wrote:

First off, I'm not even sure how to ask this correctly so bear with me

I'm trying to convince the powers that be to allow us to modernize (or at
least update) our custom code. We still have a ton of old RPG 3 (written
more like RPG 2) and way too many CLs using OPNQRYF, etc. and the question
is how is it possible to quantify this in terms of $$$. I know that I can
come up with a semi-decent guess as to man hours saved on program
maintenance but I can't even hazard a guess as to how I can calculate the
reduction in resource utilization, response times, etc. does anyone have
any ideas or methods they have used to try to at least get some inkling of
the savings of modernizing? We are currently migrating to a web based
financials (with the added bonus I get to at least do some cleanup on the
interfaces for some of this jalopy code). Since I have a small bit of
leverage during this process and we are in a holding pattern with the
vendor I'm trying to get a consultant to work on updating the existing
code to use modern techniques (i.e. Service programs, SQL, etc).

Anyway if you manage to decipher that long-winded diatribe & have ideas or
suggestions it would be MOST definitely appreciated!!!

Tommy Holden
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.

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color -- -- Verificado por Anti-Virus Corporativo Symantec --

This thread ...


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

This mailing list archive is Copyright 1997-2019 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].