× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. December 2002

RE: Tracing statements executed in debug

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Alexei Pytel

>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.


I did not know about this command! Do you mean "Type(*Trace)"?  as in:
ADDPEXDFN DFN(ABC) TYPE(*TRACE) SLTEVT(*YES) PGMEVT(*PRCENTRY *PRCEXIT)

Does any of this work without PT1?

thanks,

Steve

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.