Re: Trace ILE program lines, variables

[Dan <dbcerpg@xxxxxxxxx>]

Well, that I don't know.  I never tried Alexei's advice since my
question about tracing an ILE program was strictly academic (long
story, but my actual need was to trace an OPM Cobol program).  But I
guessed that he was referring to a solution that would generate the
same type of info that tracing an OPM program would.  I just did a
REALLY short trial of his suggestions and couldn't make heads or tails
out of what PEX generated.  Don't know whether Alexei's on this list. 
Maybe midrange-l?

- Dan

--- Dave <dschopp@imt.net> wrote:
> 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.

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