To build probe: It is reccomended that you check Probe's source, to make sure it doesn't have any obvious incompatabilities with your system (its use of Global Event Flag 52, or the clock ector address on your system). Then PROBE.CMD will build it for you. SEF.CMD works the same way. Probe's output is in the following format: ------------------------------------------------------------------------------- TASK: INTTIM: SYSTIM: USRTIM: NULTIM: TOTAL # NOT COUNTED: # TaskA # TaskB # TaskC # ... SubA1 # SubB1 # SubC1 # SubA2 # SubB2 # SubC2 # SubA3 # SubC3 # SubA4 # . . . ------------------------------------------------------------------------------- Tasks are not sorted and the ones displayed are the first K tasks caught executing, where K is the maximum number of tasks Probe was built to monitor. The subroutines for each task are displayed in a some-what sorted order, the higher the number of samples charged to them, the higher they tend to rise in the list. Task B is shown above with only two subroutines with any counts charged against them. "TOTAL" refers to the total number of samples taken. "UNCOUNTED" refers to count for which no specific subroutine was charged. To use Probe: Install and run Probe. It is now in "stasis" mode, and it is OK to abort it when in that mode (It has nothing allocated in the pool space). To start the display, set the global event flag. To stop/clear the display, clear the event flag. A small FORTRAN utility (SEF) is provided for this purpose (When SEF is installed as ...CEF it clears the specified event flag. When SEF is installed as ...REF it displays the status of the specified event flag. As ...SEF it sets it.), although any method as setting the event flag probe was built to use will work.