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



David,

I suspect you may be compiling in batch. There's a preference for this:

Remote Systems > IBM I > Command Execution (Your path in WDSC might be
slightly different)

In the section at the top (Preference for compiles ...) UNCHECK the
Compile in Batch flag.

Hth,
-Eric

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of David FOXWELL
Sent: Thursday, March 18, 2010 4:22 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Subject: [WDSCI-L] Compile error list

Hi,

Now that I have a reasonably powerful PC, I wanted to see if I could get
the compile error messages into WDSc. Currently, I compile on a
greenscreen and switch back and forth to check my errors.

I looked up EVENTF in the archives and saw I had this problem in 2007
and never resolved it.

I use a custom compile pgm on the i. I don't see what instructs this
program to create a file named EVFEVENT, but it's there with the error
messages in it.

In RSE, I've added a compile command :

CALL PGM(MyCompilePgmOnThei) PARM(&N &L &L &F) /* OPTION(*EVENTF)
SRCMBR(&N) */

This works.

Now, how do I get the error list view to show up? It does if I use
CRTRPGMOD. Eventually.

Thanks



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.