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



You should still be able to get the error message back to WDSCi.

The key is to make sure your custom command has a parameter named OPTION that takes *EVENTF as a
value.

Then when your program runs CRTRPGMOD, CRTBNDRPG, ect. make sure it specifies OPTION(*EVENTF).

HTH,
Charles


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of David Foxwell
Sent: Friday, October 26, 2007 10:41 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Compiling

Joe,

I call a standard program on the i5 for every compile.

It will create workfiles and then delete them, override file
names if a filename has to be changed in the F specs.
Also, it will work if its CLP, RPGLE or SQLRPGLE.

The downside is that I don't get the error messages returned
to WDSc of course.



----- Original Message -----
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To: "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
Sent: Friday, October 26, 2007 3:36 PM
Subject: Re: [WDSCI-L] SEP Its enough to make a grown man cry


From: David Foxwell

I've recompiled from WDSc although my recompile option calls a
program
on
the i5 that compiles for me with the right library list.

This part bothers me a little bit. This implies that your WDSC
connection to the System i does not have the library list
necessary to
compile your program. Why is that? Typically I either set up a
connection with the right library list, or I have a program
I can call
to set my library list correctly.

This shouldn't be an issue, since the debugger should get
the source
file name, library and member from the module, but it's
possible it's
getting confused and finding a different source file in the
library list.

Second is that you're using WDSC 6, but I guess you have to
live with
that for now.

Finally, I would suggest using the DBGVIEW(*LIST) rather than
DBGVIEW(*ALL).
*ALL contains both *SOURCE and *LIST information, and the
presence of
the source information may be causing the debugger to use
the source view.

Joe

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



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



This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.


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.