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




Hi David,

If I remember rightly, this has been discussed previously and compiles
go into the EVFEVENT file in the library the program is being compiled
into. Search results etc. go into the EVFEVENT file in your curlib.

Best regards,

Mark Austin
IT Consultant
Universal Music Publishing International
Email: mark.austin@xxxxxxxxxx
Tel: +44 (0) 20 8742 5520
Fax: +44 (0) 20 8742 5699

Universal Music Publishing International Limited
Registered in England. Number 02050403
Registered Office: 347-353 Chiswick High Road, London W4 4HS

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of David Wright
Sent: 26 November 2008 21:56
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] EVFEVENT file issues...

Hi All,

I have noticed another oddity that seems to have arrived with RDi
(latest updates all applied).

For some reason, the EVFEVENT file was being created in one of the
application libraries instead of my *CURRENT library. Every programmers
compiles are going into this same file.

I tried deleting all the EVFEVENT files, tried adding OVRDBF as my
initial command in the connection, but nothing seems to work.

Have I missed (or forgotten) something? I had used WDSC for years
without this issue.

Thanks,
David

PS - Happy Thanksgiving Everyone!

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.