× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks Peter,
I'm still quite new to WDSc and I'm afraid I don't understand the user
action bit.

Having said that, I have just realised that I CAN get the messages from
CRTRPGMOD etc.

This is because on the properties of the connection, I have all the
libraries necessary for compiling already on line.


----- Original Message -----
From: <Peter.Colpaert@xxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, March 22, 2007 11:35 AM
Subject: Re: [WDSCI-L] 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.

--
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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.