|
I had a similar problem when compiling C code. I thought it had something
to do with C.
It would appear to download, but it was always the same results. I am not
a C programmer and it was blowing my mind why I wasn't fixing the problem
until I finally realized it. What I did was continually delete the member
with the results from the EVFEVENT file. Now that I think about it,
perhaps the problem was that the compiler was not "updating" the member
and that is why my workaround worked.
Mark
"Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/05/2003 02:35 PM
Please respond to Websphere Development Studio Client for iSeries
To: "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
cc:
Subject: [WDSCI-L] Compile not returning events file.
I have been having trouble with my compile listing not returning to WDSc
on
a consistent basis, and today I have found a pattern.
I am compiling using the CRTRPGMOD command
CRTRPGMOD MODULE(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) OPTION(*EVENTF)
REPLACE(&R) DBGVIEW(*LIST) TGTRLS(V5R1M0)
and I only get a compile listing back on the first compile of this program
after opening WDSc. ??
Any suggestions? archive.midrange.com is down right now, so I don't know
if
this has already been addressed.
Aaron Bartell
_______________________________________________
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 mailing list archive is Copyright 1997-2025 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.