Re: CPF19812E File QSQLTEMP1 in Library QTEMP not found

I agree and I *really* hated getting that same scratch on my "new car".

Here's what I do using SoftLandings RSE Extensions:

1) I configure 'Remote Systems', 'iSeries', 'Command Execution' in 
preferences to 'Add batch compiles to the iSeries Job Status view'.

2) Then after submitting a compile, I open 'iSeries Job Status view'.

3) Right-click on the last job and select 'Spooled Files'.  (This 
parallels option 8 on green screen WRKSBMJOB.)

4) Then I open the compile listing and search for ': 30' or ': 20' or 
whatever level of errors I'm looking for.  The error message gives me the 
line number from the original source member.

5) Then I go the program source and use Control-L to go to the line and 
fix the source error.

Like you say, "awkward", very awkward and far from ideal -- a little more 
cumbersome than SEU, but at least I can keep working on it.

I'm believing this is a high priority for IBM to handle.  We're told we 
should switch to SQL and WDSC, but it's a big step backwards.  (I guess 
we're supposed to never make a mistake in our programming <grin>).

Michael Quigley
AS/400 Programming Coordinator
The Way International
www.TheWay.org

Original message:

------------------------------
date: Wed, 8 Feb 2006 16:04:44 -0500
from: "Fleming, Greg \(ED\)" <GFLEMING@xxxxxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] [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.