Subject: Re: CEETRACE Listing Imbed?
From: Garry Hasler (lezvse@aapt.net.au)
Date: Thu Nov 12 2009 - 18:17:03 EST
Hi Kevin, Glad to hear its working now. Is the PDF you refering to online? If so could you please let me know the link? Then I can see if there's anything I can do to improve the documentation. I'd just point out too that Debug Tool has nothing to do with the SYSDEBUG support nor can currently it use it (there is an open APAR to change this at the moment). The reason I chose the SYSDEBUG member over the .LIST member was so that anyone can use CEETRACE with COBOL source code support and not be dependant upon having Debug Tool available. Your statement about how Debug Tool and CEETRACE are useful is exactly what the tool was designed for. Regarding your query about the "exclude" partition list and CEETRACE enhancements I will say that CEETRACE is actively being developed and improved so keep an eye out for changes in subsequent z/VSE releases. Cheers, Garry Hasler ADL/z West Perth, Australia > I got it working. It was the SD parameter, fully expressed with the > lib.sublib(member) construct that was missing. The documentation in the PDF > does not make this clear at all. The current online documentation for > COBOL, LE/VSE, and Debug Tool has very little mention of any of this. I > would assume that when SD (SYSDEBUG) is passed on the parameter, it would > automatically generate the <program>.SYSDEBUG member into the default > library, just like the <program>.LIST member used for Debug Tool, this was > not the case. Anyway, it's now working and my compile procedures have been > updated to provide all that is needed for CEETRACE and Debug Tool. The > trace can be very useful for simple debugging tasks while Debug Tool is more > apporpriate for complex problem resolution. > > > > >
This archive was generated by hypermail 2b25 : Tue Nov 24 2009 - 16:05:07 EST