|
I've been in your shoes before, and it's painful no matter how you look at it. We had numerous programs like this and here's what we did for that project. First, we put together programs specs to identify exactly what the program did, and why. Then, we identified the useful code in the program (which there wasn't a lot of), such as detailed calcuations or subroutines that could be used with minor changes. Then we rewrote the screen processing portion of the program. Basically, we ended up rewriting every screen processing program. Sometimes we found some code that just didn't make sense, and instead of taking time to figure it out, we filled the necessary variables as they had been filled in the previous program and let the code run. Good luck!! +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.