Re: [BULK] Re: CPF19812E File QSQLTEMP1 in Library QTEMP not found

It didn't help though.

The fundamental problem still remains, and at least I understand it more
clearly now.

It seems that the SQL precompiler creates an expanded copy of my source,
which is what actually gets compiled. So the best case scenario for
retrieving error messages is to open the expanded source member, look at
the errors, then go back to my original source member and fix them. And
even that requires establishing a permanent source file where these
expanded source members will reside.   

I'm thinking that going to the green screen to look at my compile errors
is probably better.  

Now I'm kind of sad.  I'm really digging WDSC, but it's kind of like
finding that first scratch on your shiny new car, or suddenly realizing
that it doesn't have cruise control. 

It's awkward, but I guess I'll get used to it.    



|-----Original Message-----
|From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
|Behalf Of Fleming, Greg (ED)
|Sent: Wednesday, February 08, 2006 3:38 PM
|To: Websphere Development Studio Client for iSeries
|Subject: [BULK] Re: [WDSCI-L] CPF19812E File QSQLTEMP1 in Library QTEMP
not
|found
|Importance: Low
|
|I found it...(in case anyone else is looking)
|
|In the preferences, Remote Systems > Preferences > Command Execution,
|then check (or uncheck) the "compile in batch" box.
|
|
|