Re: Compiling SQL RPGLE

Hello Justin,
I do use Verify. Thing is Verify just is not reliable to find all
SQL errors. In particular it does not seem to be able to find
the errors that the SQL pre-compiler finds.
This is very easily demonstrated. Just remove a : from a SQL
host variable. Verify does not detect the error.
The pre-compiler finds it with the message.
'SQL0206 Position 25 Column #SAPN not in specified tables.'

oops the precompiler strikes again.

Frank Kolmann

date: Tue, 30 Oct 2007 12:59:30 -0500
from: "Justin Taylor" <JUSTIN@xxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Compiling SQL RPGLE
Use Verify.

------------------------------

date: Wed, 31 Oct 2007 09:05:31 +1100
from: Frank.Kolmann@xxxxxxxxxx
subject: [WDSCI-L] Compiling SQL RPGLE

Thanks Thierry,
Good Tip.

date: Mon, 29 Oct 2007 22:35:11 -0400
from: Thierry Bernard <thierry.mr@xxxxxxxxxx>
subject: Re: [WDSCI-L] Compiling SQL RPGLE
I agree. In the meantime, on the Create command, CRTSQLRPGI, there is

a

ToSrcFile parameter that you can specify where the RPGLE source
generated by the precompiler can be saved, say &L/SQLRPGLETMP. Then

when

you double-click an error, it will open that generated source member

and

position you to the line. Of course, you don't want to change that
member, but your original source but at least you have the error in
context (think of it as looking at the listing).