Subject: RE: CEETRACE Listing Imbed?
From: Kevin Corkery (kcorkery@live.com)
Date: Thu Nov 12 2009 - 12:04:45 EST
The partition "exclusion" list would be useful, since it's limited in size, if you could exclude by dynamic partition class. For instance, I would like to exclude all of my interactive DITTO partitions. The list limit does not permit me to ennumerate all the partitions in the class. Maybe supporting a wildcard would be desireable although this is specifically mentioned as not supported in the documentation. Another alternative would be to make the list an "inclusion" list? Since we run development and production in the same zVSE image I'd really like to restrict the CEETRACE functionality to the test partitions/classes only. Anyway, thanks Garry for you guidance. -----Original Message----- From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Kevin Corkery Sent: Thursday, November 12, 2009 10:58 AM To: VSE Discussion List Subject: RE: CEETRACE Listing Imbed? 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. -----Original Message----- From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Garry Hasler Sent: Thursday, November 12, 2009 2:55 AM To: VSE Discussion List Subject: Re: CEETRACE Listing Imbed? Hi Kevin, What CEETRACE is referring to here is not the .LIST member that the DT/VSE PRTEXIT EQALIST produces, but the .SYSDEBUG (side-file) member that the compiler produces (no exits required for this). This is a separate librarian member. It is not part of the compiler produced OBJ or the linkedit PHASE. Did the COBOL/VSE compiler listing output show that the compiler honoured your TEST settings? Did you have the SD option specified on the JCL PARM card for the // EXEC IGYCRCTL? And finally, do you have the side-file COBOL/VSE compiler PTF(s) installed? They are referenced in the CEETRACE documentation. Let me know the answers to the above and we will work from there to find out why you are not getting the source code shown in your execution trace report. Cheers, Garry Hasler VM/VSE Systems Programmer ADL/z West Perth, Australia > I'm trying to use CEETRACE to get a trace listing during abend > processing. I'm compiling like I would for use of Debug Tool and > getting a <program>.LIST member in the same library as the > <program>.PHASE. When I run the program and cause an ABEND I get the > trace but no married source. > > VSECON00I STARTING ON: 11/11/09 AT > 16.24.12 > > VSECON01I COMPILED ON: 11/11/09 AT 16.23.29 VERSION: > 08 > > VSECON30I PROCESS WAS DELAYED BY REQUEST FOR 1 > SECONDS > > VSECON20I SIR > RC=00 > VSECON45C USER REQUESTED ABEND INITIATED => > *ABEND=64 > > > > CEETRACE Program Execution Trace Report > Begins > > > > Date Time Program_Name Entry_Name Stmt# Stmt Offs > Stmt_Lang Statement Source Code > 11/11/2009 16:24:15.17 VSECON Ent/Ext/Par N/A. > +00001226 COBOL External Entry/Exit point, End clause or Paragraph > */11/11/2009 16:24:15.17 VSECON VSECON 468 > +0000122A COBOL Program not compiled with the SEP option. > /* 11/11/2009 16:24:15.17 VSECON Ent/Ext/Par N/A. > +00001256 COBOL External Entry/Exit point, End clause or Paragraph > 11/11/2009 16:24:15.17 VSECON VSECON 473 > +0000125A COBOL Program not compiled with the SEP option. > 11/11/2009 16:24:15.17 VSECON Ent/Ext/Par N/A. > +00000B50 COBOL External Entry/Exit point, End clause or Paragraph > 11/11/2009 16:24:15.17 VSECON VSECON 373 > +00000B54 COBOL Program not compiled with the SEP option. > 11/11/2009 16:24:15.17 VSECON Ent/Ext/Par N/A. > +00000CF8 COBOL External Entry/Exit point, End clause or Paragraph > > I am compiling with TEST(ALL,SYM,SEPARATE) but for some reason the > "options in effect" indicates TEST(ALL,SYM,NOSEPARATE) but I do get > the listing in the library, not imbedded in the load module. Any > ideas as to something that I'm missing. TIA. > > Kevin P. Corkery > Independent Consultant > Voorhees, NJ 08043
This archive was generated by hypermail 2b25 : Sun Nov 22 2009 - 16:35:07 EST