Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!uflorida!haven!decuac!pa.dec.com!bacchus!mwm From: mwm@raven.relay.pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.lang.rexx Subject: Re: REXX Profilers? Message-ID: Date: 30 Nov 90 21:53:32 GMT References: <90334.131137BEBO@SLACVM.SLAC.STANFORD.EDU> Sender: news@pa.dec.com (News) Organization: Missionaria Phonibalonica Lines: 14 In-Reply-To: BEBO@SLACVM.SLAC.STANFORD.EDU's message of 30 Nov 90 21:11:37 GMT In article <90334.131137BEBO@SLACVM.SLAC.STANFORD.EDU> BEBO@SLACVM.SLAC.STANFORD.EDU (Bebo White) writes: I am interested in tools for "profiling" REXX programs. By this I mean monitor how much execution time is spent in each loop, procedure, etc. (Similiar to FORTRAN hot spot analysis). I did a statement count profiler as an exercise. It's got some (known) problems, but converting it to a time profiler (with problems intact) would be straightforward. Fixing the problems would be more complicated. It's written in ARexx, and may require some work to convert to another dialect. Ask for a copy if you want it.