|
Joel, I think the reason is more political than pragmatic - the sql precompiler is done by a different team than the rpg compiler. (toronto vs rochester?) that also explains the differences between the two commands when it comes to ILE related parms. rick Joel Cochran <jrc@xxxxxxxxxx> To: rpg400-l@xxxxxxxxxxxx Sent by: cc: rpg400-l-bounces@x Subject: Learning new stuff... idrange.com 08/01/03 04:44 PM Please respond to RPG programming on the AS400 / iSeries I want to once again thank this list for being outright awesome. I learned something yesterday that was once again completely contrary to the way I thought things were: I learned (I think courtesy of Mark Walters and apologize if that is wrong) that you can mix SQL and regular file access in the same source member. For whatever reason, I had always been under the assumption that the two don't mix, that you had to use one or the other. While I have used QSYSPRT in SQL programs, I figured spooled out put was an exception. So much for assumptions. So why bother the list with this? To clarify the issue in case anyone else was under the same impression and to own up to occasionally feeling downright dumb. I'm sure we can all relate on some level. A legit question that comes to me though is this: if I can mix the two, why do we have two RPGLE source types? Why must I specify SQLRPGLE instead of RPGLE? If the answer is to signal to the compiler to use the SQL pre-compiler first, then why not just scan the source file for a "/Exec SQL" label instead? I'm not trying to make waves, just trying to become enlightened ;-) Have a great weekend, Joel http://www.rpgnext.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.