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



Would it be possible for WDSCi to then delete that file after it retrieves the information from it?

Sean

Violaine Batthish wrote:
Hi Sean,

Events files are created by the compilers when the parameter
OPTION(*EVENTF)  is specified.
As you have observed, the events file is usually generated in the same
library as the compiled object .
There is no way to tell the compiler to place the events file in a
different library.

Events files are needed by the RSE in order to display compile errors in
the Error List.
I believe you could modify your compile commands and remove the *EVENTF
option, but then you would no longer see compile errors in the Error List
view.


Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab




wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/09/2005 04:13:35 PM:


Is there any way to stop WDSCi from creating the EVFEVENT files all over
the place?  I don't mind having one in my library, but I can't be
creating extra objects all over the system.  The "compiled objects"
reports for the auditors will pick that up with my name on it and no
approved task to match.

The help I found says it is created in the library where the object is
to be created.  Can that be overridden?

Version: 6.0.0.1
Build id: 20050214_1800


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.