Re: How to view compile errors

David,

we also have a home-made compile command, and it does return the errors to 
the RSE.

You only need to include an extra parameter to the actual compile command, 
and to the user action in RSE.

For instance (in the CL behind our compile command):

CRTBNDRPG  PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) OPTION(*EVENTF)
             DBGVIEW(*ALL) TGTRLS(*CURRENT) 

And the user action command string:

OVRCMP SRCFILE(&F) SRCLIB(&L) SRCMBR(&N) OBJLIB(&L) MBRTYPE(&T) 
SUBMIT(*NO) LOCREM(*REMOTE) /* *EVENTF SRCMBR(&N) */

The *EVENTF options make sure that the compile errors (if any - I never 
have compile errors hehe) are returned to WDSCi.

Just one bummer: it doesn't work for SQLRPGLE (because the actual source 
member is in the QTEMP of the submitted job)

HTH,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



"David Foxwell" <david.foxwell@xxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
22/03/2007 11:28
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] How to view compile errors






My advice would be stick to your green screen.
For controling errors anyway.

I can rarely use the supplied compile command which would be great because
the errors are displayed and u can simply clic on them to find them in the
source. I have added my own compile command which obviously doesn't return
the errors to WDSc. When I'm compiling the same program often, I will have 
a
green screen with the source of the program open with SEU option 5, and a
split screen to view the compiled source.