|
Dan <dbcerpg=/E1597aS9LQAvxtiuMwx3w@public.gmane.org> helped spread the news by saying: > Dave, in my research last month for tracing statements in Cobol, > Alexei Pytel offered: > > There is a way to trace ILE program (procedure call/return trace): > 1) compile with option ENBPFRCOL(*ENTRYEXIT) or ENBPFRCOL(*FULL) > 2) collect data by PEX with a PEX definition defined with > TRCTYPE *SLTEVT)SLTEVT(*YES) PGMEVT(*PRCENTRY *PRCEXIT) > (ADDPEXDFN command) > 3) then use PRTPEXRPT command to print trace report > > PRTPEXRPT command requires PT1 product. Also you will not see actual > source statements, but it will show procedure call/return trace for > ILE programs. <snip> >> Does anyone know of a top-secret utility (or method) to print the >> source >> lines and variable values of the executed lines in an ILE program? So... this is going to show me... CALL and RETURN info, correct? Doesn't help me a bit, sorry to say. -- David Schopp WISDM Team Leader Computers Unlimited
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.