× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Using % type functions/using RPG IV
  • From: John P Carr <jpcarr@xxxxxxxxxxxx>
  • Date: Sun, 6 Feb 2000 17:26:16 -0500



>Jim,
>Personally, I quit converting RPG II to RPG IV.

I personally would have to agree in most cases.  
Look at the inputs, look at the desired output,
Rewrite what's in between.  The business rules
and how they were implemented are probably 
jaded anyways.

I know that the word "Re-Write" conjures fear
and loathing as an initial reaction by most 
people,  but,   I have found I can do it faster
and have a better output than "Enhancing" 
old code. 

Over a year's period the cost is must less
I firmly believe.

If you don't have a skeleton program for the
3 or 4 major program types to clone from,
you are already doing more work than 
you should.    

Question,  does every subfile program
and every report program in your shop
use the exact same mechanics??

If not,  you have a standards problem,
not a language problem.

If the answer is yes,  then once you 
done one,  the rest should be simple.

John Carr

+---
| 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 thread ...


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

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.