Imbedded SQL -Compile Errors

The comment chain (copied below) was from 3/2004.  Has this issue been 
resolved?  The 6.01 version of WDSc still appears to have this problem in 
11/2006.

Sam,

I can see how frustrating that would be!  Currently there is no solution /
workaround for the scenario you are seeing now, but enhancing SQL support
in WDSc is one of our main initiatives for the RSE and this is on the list
of things to be addressed.

Thanks, we really appreciate the feedback (both the good and the bad.)

Don Yantzi
WebSphere Development Studio Client for iSeries
IBM Toronto Lab
Phone: (905) 413-4476
IBM internal:  IBMCA(yantzi)  -  Internet: yantzi@xxxxxxxxxx



 
             "Samuel J Lennon" 
             <lennon_s_j@hotma 
             il.com>                                                    To 

             Sent by:                  wdsci-l@xxxxxxxxxxxx 
             wdsci-l-bounces@m                                          cc 

             idrange.com 
                                                                   Subject 

                                       RE: [WDSCI-L] Retrieving compile 
             03/05/2004 01:50          errors with SQL RPG 
             PM 
 
 
             Please respond to 
                 Websphere 
                Development 
             Studio Client for 
                  iSeries 
 
 




   Don, thanks for the comment.

   I changed the CRTSQLRPGI command to put the pre-compiler file in my
   personal library.

   My first compile has SQL errors. I get them back in the error window .
   This is good, but I can't insert them into the source.

   I fix the SQL errors, and recompile. Now I have compile errors. I 
double
   click on an error message to insert the messages. WDSC goes out to the
   iSeries to download something, then I see error messages inserted in 
the
   source. Joy!

   I fix the errors and click compile. No CRTSQLRPGI choice! Then I 
realize
   that WDSC downloaded the pre-compiler temporary file and I've fixed the
   errors in that source. Not what I want. (Thump forehead for not 
noticing
   another window had opened.)

   I fix the errors in the real source and try again. Being fat-fingered I
   still have errors. I insert the errors again, and even knowing better, 
I
   still attempt to correct the temporary source. (Thump forehead again.)

   At this point, I'm still of two minds whether compiling on the green
   screen and Alt-Tabbing between SEU and WDSC isn't a better option than
   having a temporary source member open in WDSC with errors inserted.

   I'm still inclined to stand by my opinion that WDSC is less than
effective
   for embedded SQL. Is there any other work around that I am missing?

   Sam

   >From: Don Yantzi <YANTZI@xxxxxxxxxx>
   >Reply-To: Websphere Development Studio Client for
   iSeries<WDSCI-L@xxxxxxxxxxxx>
   >To: Websphere Development Studio Client for iSeries
   <WDSCI-L@xxxxxxxxxxxx>
   >Subject: [WDSCI-L] Retrieving compile errors with SQL RPG
   >Date: Thu, 4 Mar 2004 16:41:17 -0500
   >
   > >>1) SQL embedded in RPG.  Can't get the compile errors back.
   >
   >Sam,
   >
   >Do you not see the error list coming back, or you get the error list
and
   >can't double click on errors?  If it is the latter then you will need
to
   >use the TOSRCFILE parameter for the CRTSQLRPG command to change where
the
   >temporary source file created by the SQL preprocessor gets generated.
By
   >default this is QTEMP which the RSE cannot access after the
   compile.  When
   >the RPG compiler generates error messages the messages reference lines
in
   >this temporary file.
   >
   >Don Yantzi
   >WebSphere Development Studio Client for iSeries
   >IBM Toronto Lab
   >Phone: (905) 413-4476
   >IBM internal:  IBMCA(yantzi)  -  Internet: yantzi@xxxxxxxxxx


Thanks