|
Hi Jim, All of your points are valid (and you have my sympathy having to work with this code), but they apply when converting RPG II to RPG III. I think the real point here is in going from RPG III to RPG IV. I know, there is still a lot of 36 code out there, but there is an awful lot more 38/400 code which is ripe for conversion to RPG IV. I go with Bucks learning curve, I just think we have to be honest and add 10 minutes for the new format of the F Spec and the D Spec ;-) By the way, wasn't there an RPG II to RPG III conversion tool out there at one stage? Paul Jim Langston wrote: > Well, take for instance the program I am converting to RPG IV from > RPG II. My boss wanted me to modify a program to do some selection > on a report. The current report goes through the entire file looking for > data that meets certain criteria and once finding it in the primary chains > to a bunch of other files and grabs data, then prints it. > > <snip> > > Time involved converting RPG II to RPG IV 5+ > > Now, if I was writing this from scratch, it would be much, much faster to > write it in RPGIV then RPGII, but legacy exists. > > There is good and bad in this though. My new program is going to be > ILE, or RPG IV anyway, I'm not going to link anything to it. The original > program I copied this from, however, is still RPGII. Argh! > +--- | 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-2025 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.