|
Yeah, Booth, I'd thought of that. Personally, I'm not too enamored of the AFP Viewer. It is nice, tho', to drag a spooled file to a folder or the desktop. (Does an AFPDS spooled file come through with the graphics with drag-drop? Nope, text only. Bummer.) Vern At 01:46 PM 11/15/2002 -0500, you wrote:
Now I am catching up. Why not use Ops Navigator? That shows spooled output in a nice way. Granted it isn't in Code400, but it's there and able to be used. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: code400-l@midrange.com Date: Friday, November 15, 2002 01:13:28 PM To: code400-l@midrange.com Subject: Re: Code compile results - how to see? Hi Booth The original message asks about compile completion messages (which we get) and compile listing (which we don't). You have to go to the 400, whether via the STRCODE session or some other, to see the spooled file that has the listing. It IS known to the process, I believe, so it COULD be made available. BTW, verifier output does nothing for C/C++ development, as I've bemoaned in other posts. One reason I like to see C listings is that I can see the include stuff, as well as macro expansions. I don't think macro expansions show up in the error list, just the error. We C developers need a lot more help from this thing, else we might as well use CodeWright or TextPad or ez (one of IBM's Andrew toolkit-based developer tools). Regards Vern At 12:12 PM 11/15/2002 -0500, you wrote: >I have been curious in this thread as to what information he is looking for >when the program compiles successfully? Perhaps what he is looking for can >be found in some other way? Or perhaps he could set his threshhold for >errors at 10? > >--------------------------------------------------------- >Booth Martin http://www.MartinVT.com >Booth@MartinVT.com >--------------------------------------------------------- > >-------Original Message------- > >From: code400-l@midrange.com >Date: Friday, November 15, 2002 08:44:17 AM >To: code400-l@midrange.com >Subject: Re: Code compile results - how to see? > > >>But there is no way I can see to see the spooled output from the compile > >>without going to an emulation session. > >As far as I know we do not have other function in CODE for viewing SPL >files. That is why we provide error list and verifier output. > > >Best regards, >Hak >_______________________ >Hak Lui >AS/400 AD, IBM Canada Ltd. >e-mail: haklui@ca.ibm.com > ________________________ _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange com/cgi-bin/listinfo/wdsc-l . _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-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.