Mark,
It isn't WDSCi that controls where the event file is placed. It's the compiler that does it. Here's the V5R4 help text for OPTION(*EVENTF) from CRTBNDRPG:
"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.
CODE uses this file to provide error feedback integrated with the CODE editor. An Event File is normally created when you create a module or program from within CODE."
We'll ignore the fact that the compiler help hasn't been updated in an eon or so. ;) Based on what this says, the *CURLIB setting on the user profile only affects the location of the event file if the program is being compiled into *CURLIB and if the *CURLIB hasn't been changed in the user's library list since the user signed on. This is consistent with what I see on my system.
Unfortunately, I can't find any comparable information on how the Search function decides where to put the event file. Maybe it does use the *CURLIB - I can't be sure. Anyone else know?
As it stands right now, I think changing this would be difficult for IBM to justify, since it would probably involve coordination with 3 different teams (WDSCi, compilers - which involves several sub-teams, and PDM), and it WOULD break support for CODE, which is still in widespread use but isn't likely to be updated for something like this. Would the gain be worth the cost?
Dave Shaw
Mohawk Industries
----- Original Message -----
From: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Friday, November 02, 2007 8:42 AM
Subject: Re: [WDSCI-L] Compiling
I have seen this issue or problem come up over and over again, in
several different contexts, including compile problems (with getting the
errors back) and when running the WDSCi equivalent of FNDSTRPDM ...
It occurs to me that IBM could fix this problem by making WDSCi do the
following -- if a user profile has *CRTDFT for CURLIB, use the user
profile name as the library name; if it doesn't exist, create it
automatically, and place the event file (EVENTF) in this userID library
(in lieu of *CURLIB).
DeLong, Eric wrote:
Perhaps you need to look at your user profile and make sure it's not CURLIB(*CRTDFT)....
Eric
midrange.com
