×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




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.

HTH, Dan

--- Dave <dschopp@imt.net> wrote:
> Using the 3rd party product RPGTRC, I am able to print the lines
> executed 
> by a program, along with the values in each variable.  Tremendous
> program - 
> priceless.
> 
> Now, I'm working with a new ILE program.  RPGTRC doesn't work with
> ILE 
> programs, only OPM.  Debug also only traces OPM objects.
> 
> 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?

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.