RE: Embedded SQL compile error - Correction

I use a procedure similar to Alan Campin's.

However, rather than changing the module, all you need to do is open the source in RDI and then go to the compile menu and select the non-sql compile option.
CRTBNDRPG or CRTRPGMOD

You don't even need to worry about "Compiling to QTEMP" since the compile will fail when it sees the sql code.

To reiterate, the goal with doing this is to allow the regular compiler errors to be shown so you can address them.
Most likely cause is a definition issue with the data structure.


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Alan
Campin
Sent: Wednesday, May 5, 2021 3:39 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Embedded SQL compile error - Correction

My trick for solving these kinds of problems is change the module or
program to be a regular RPG member and then do a 15 in PDM to compile
and
compile to QTEMP.

Now it won't compile obviously but you will be able to see RPG errors that
are keeping the SQL compile from working like a bad data structure.