Hmm, not on my system when using the CRTBNDRPG command. In fact, the help text for the command says that when the *EVENTF option is used:
"Create an Event File for use by CoOperative Development Environment
(CODE). The Event File is created as a member in file EVFEVENT in
the library where the created module or program object is to be
stored. If the file EVFEVENT does not exist it is automatically
created. The Event File member name is the same as the name of the
object being created."
Which I "tested" by compiling a program that is not in my *CURLIB (rather, in one of my Project/Test libraries). The EVFEVENT file showed this compile feedback. Even though the Help text refers to CoDE, this would, also, be the source for the iSeries (sic) Error List in WDSc.
But, then, I didn't test with any other compile commands.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Sent: Friday, September 26, 2008 8:24 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Current library question
Jerry Adams wrote:
What "stuff" are you talking about, Jim? Although my current library isn't QGPL, there's nothing from WDSc in my *CURLIB. At least, not unless I tell it to do it.
EVFEVENT holds the information from the compiler. That lives in *CURLIB.
--buck
--
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.
midrange.com
