• Subject: Re: Dynamic embedded SQL (in RPG) example -Reply -Reply
  • From: Scott Cornell <CORNELLS@xxxxxxxxxxxxxxx>
  • Date: Mon, 06 Oct 1997 11:47:20 -0400

>>> "Art Tostaine, Jr." wrote >>>
  <<snip>>
>
> C/EXEC SQL
> C+ EXECUTE IMMEDIATE :$SQL
> C/END-EXEC
>

  <<snip>>

> Can this type of program be compiled on a
> client system that does not have SQL/400
> installed?

            ----------

Nope, I should have been more clear - we
have SQL/400 on our development system.  I
wrote & compiled the code here, then
restored the pgm object on the client
systems that don't have SQL/400...works
just fine.

One tricky work-around thing you might try
- you can save the intermediate source
generated by the SQL pre-compiler (it ends
up in QTEMP I believe and you can copy it
from there to a permanent source file). 
The pre-compiler replaces all EXEC-END EXEC
blocks w/"normal" calls to the appropriate
system API's.  To the extent that the pgm
object *DOES* work on systems w/o SQL/400
(indicating the API's exist even if SQL/400
isn't installed), I would suspect that the
pre-compiler massaged code would also
compile on those systems...actually, given
OPM non-bound calls, it should compile,
even if the called pgm doesn't exist.  Heck
it might even work correctly too.  A brave
new world to experiment with, if you're so
inclined. :)

Scott Cornell
Mercy Information Systems

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


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

This mailing list archive is Copyright 1997-2019 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].