RE: Tracing statements executed in debug

[Alexei Pytel <pytel@xxxxxxxxxx>]

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

This is correct.

> Does any of this work without PT1?
PRTPEXRPT command is part of PT1 - ADDPEXDFN, STRPEX and ENDPEX are all
system commands.
ENDPEX will create a bunch of QAYPExxx files, which have all the data, but
PRTPEXRPT will convert the data to readable format.

  Alexei Pytel
always speaking for myself






                      "Steve Richter"
                      <srichter@autocode        To:       
<midrange-l@midrange.com>
                      r.com>                    cc:
                      Sent by:                  Subject:  RE: Tracing 
statements executed in debug
                      midrange-l-admin@m
                      idrange.com


                      12/17/2002 07:19
                      PM
                      Please respond to
                      midrange-l







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



thanks,

Steve


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.