Re: Compile SQLRPGLE in WDSC vs Green Screen.

["Brian Johnson" <brian.johnson.mn@xxxxxxxxx>]

F15 is from SEU, to browse the compile listing in split-screen mode.

WDSCi can't find the source because the SQL source comiled is the SQL
pre-compier output in QTEMP/QSQLTEMP1, and that source file is not
accessible when you click in the iSeries error list view.  QSQLTEMP1
apparently exists in the QTEMP library of a different job.  Modifying the
create command, either with COMPILE or a modified WDSCi create command,
places the compiled source in a permanent library, so any job can access it.

Note that with either method, when you natvigate to source from the error
list view, the source in QSQLTEMP1 is opened and errors shown.  That's not
the source you want to edit.  Make sure you switch to the editor of the
"real" source to fix those errors.


On 3/22/07, Fleming, Greg (ED) <GFLEMING@xxxxxxxxxxxxxxxxxxxx> wrote:
> |If I compile a program in PDM and then do a F15, type 2 and then search
> |for *err, I find the errors. Now the important thing here that when the
> |compile runs, it is submited to batch. It is still being compiled to
> |QTEMP but it finds the error without any problems.
>
>
> Alan,
>
> >From where are you doing the F15 ?  When I compile in PDM, I do so from
> the
> "Work With Members Using PDM" screen using option 14.  From this screen,
> F15 is "Sort Date" which just sorts all the members by date.
> What am I missing ?
>
> thanks
>
> --
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
> mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.