|
Anton, does your compile command have parameter SRCMBR(mbrName) and OPTION(*EVENTF)? WDSC should show the errors if you have these two parms in your compile command. Kushal Munir Websphere Development Studio Client for iSeries IBM Toronto Lab, 8200 Warden Ave., Markham, ON Phone: (905) 413-3118 Tie-Line: 969-3118 Email: kmunir@xxxxxxxxxx Anton Gombkötö <gombkoetoe@assof To: WDSCI-L@xxxxxxxxxxxx t.com> cc: Sent by: Subject: [WDSCI-L] What is *CURLIB/EVFEVENT? wdsci-l-bounces@m idrange.com 09/22/2003 03:42 PM Please respond to Websphere Development Studio Client for iSeries Hi *ALL, i've succesfully inserted our own compiling command into the "compile commands", but when i run it, i receive "CPFI9812E File EVFEVENT in library (my current library) not found." in WDSC 5.1 when it completes. (The fact that &S for the member type is no longer supported, was a bit annoying, but as it isn't possible to configure a more general (smart) compiling command, i hardcoded our parameter MBRTYPE(&S). In order to get existing customers a bit easier aboard, it would be nice to support &S.) What can i do with this EVFEVENT file? The name implies that i could make it do something in WDSc. At least i'd like it to make the error disappear... ;-) Can i use it to display the result of compilation? Thanks in advance! Anton Gombkötö Avenum Technologie Gmbh http://www.avenum.com Vienna, Austria, Europe _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
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.