Re: RPG and SQL Compilers

 >> All IBM needs to do is 'Sunset Clause' a particular interface,

I'm not sure "All" is as simple a word as you make it sound - witness the
fact that when I was with IBM we had to keep PL/I alive more than three
releases after we originally said we were withdrawing it!  If you want more
evidence look at the current fuss over OV/400.

It is a good idea though - I keep telling them they should announce the
withdrawal of RPG/400 - that would get SSA, JDE and a few others off their
asses and let their customers move on!

 >> I was thinking to use the IRP (does this still exist)

Yes but I suspect that the two compilers use different IRPs - RPG IV uses
W-code (which becomes MI-prime) and I suspect SQL still uses MI.
Regardless I don't see how it helps other than to avoid having to generate
additional source statements in the RPG code - and this compiler technique
allows for that.

 >> Sounds good.  I assume that any compilation requires multiple passes
over the source.

No.  Compilers using this technique (known sometimes as Inner-Outer)
require only a single pass.  There are some things that can't be done "on
the fly" as indeed there is with the current RPG and COBOl compilers, but
once the RPG compiler knows that it has invoked the SQL compiler, then it
can call it again at the end of the compilation so that SQL can go through
it's own fix-up phase(s).



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