|
Have a look at OPTION(*EVENTF) on the compiler commands. *EVENTF Create an Event File for use by CoOperative Development Environment/400 (CODE/400). 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/400 uses this file to provide error feedback integrated with the CODE/400 editor. An Event File is normally created when you create a module or program from within CODE/400. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 > -----Original Message----- > From: ed_doxtator@baxter.com [mailto:ed_doxtator@baxter.com] > Sent: Tuesday, November 05, 2002 12:34 PM > To: midrange-l@midrange.com > Subject: Fetching RPGLE compiler errors > > > > Hey All > > Are there any APIs to invoke the RPG compiler in V5R1? I'm > trying to sort > out a way to fetch compiler error messages without having to > comb through > the resulting spool file. Is there something similar to what > the ILE C > compiler does (that is, send compilation messages to the joblog)? > > Thanks! > > -Doc > > ----------------------------------------- > Ed Doxtator, Analyst > Baxter International Healthcare > 1435 Lake Cook Road, LC II-3 > Deerfield, IL 60015 > Voice: 847-940-5680 > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.