Re: SQLRPGLE Compile Errors

On 7/31/2013 2:08 PM, Robert Mullis wrote:

When I compile an RPGLE source and get errors, I get the error listing.
Clicking on an error in the error list takes me to the line in the
source member with the error and inserts the error text underneath the
source line. This does not happen when the source member is a SQLRPGLE.
I still get the error list and am able to click on the error, but it
does not go to the source for the SQLRPGLE. Instead, RDp opens the temp
source created by the SQL precompiler in EVFTEMPF and goes to the line
in that temp source. I then have to go to the actual source member to
make the correction.



Is there a way to get SQLRPGLE compile errors to go to the actual
source, instead of the temp source in EVFTEMPF? I am running RDp 8.5.1
on V5R4.

Lpex has been showing me the errors in the regular source for as long as
I can remember - at least WDSC 7.0.0.8. But I do recall having to do
something to get there. I looked at the wiki to see if it had the
secret sauce and it did.
http://wiki.midrange.com/index.php/WDSC_tips/Compile#SQLRPGLE_Compiles_how_to_find_Compile_errors

I compile 'interactively' (which is a misnomer because the 'interactive'
job is really a server job running in batch!)

I use this command when compiling my SQLRPGLE:
CRTSQLRPGI OBJ(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) OPTION(*EVENTF)
RPGPPOPT(*NONE) REPLACE(&R) TOSRCFILE(*CURLIB/QSQLTEMP1)
COMPILEOPT('DBGVIEW(*LIST)')

If the wiki is unclear, please take a crack editing it to make it better
for future readers. You particularly have a good perspective on what is
missing / unclear because you are about to configure RDP the way you
want it to become. Which is exactly why people will want to read that
wiki entry...
--buck