RE: Trace ILE program lines, variables

[Dave <dschopp@xxxxxxx>]

"M. Lazarus" <mlazarus=Z876VzW3xUs@public.gmane.org> helped spread the
news by saying: 

> Tom,
> 
> At 1/8/03 09:04 PM, you wrote:
>>There've been maybe half a dozen times in the past ten years where a
>>trace of the last hundred or so statement numbers was useful to me,
>>and I've twice missed having that capability in ILE. But I'm lost in
>>understanding why there's significant value beyond that.
>>
>>Can you describe its value for you?
> 
>   I can think of one besides debugging - program profiling.  Some
>   items 
> that can be determined:
> 
> -  Is every statement being touched (very useful during testing)?
> -  Where is the program spending most of its time?
> -  During testing, if variable changes are tracked it can be an eye
> opener finding out that a counter might be approaching the maximum,
> etc. 
> 
>   -mark
> 


Old program was S/36, rewritten to ILE.  (Rental) order entry.
First screen offers user 10 different options, each initializing work and 
file values, specific to the option.  3rd screen has over 40 fields that 
continue to affect "down-stream" values.  Final screen is invoice totals 
and payment information.  I need to make sure the data coming out the back 
end coincides with options taken and values entered.  

Trust me - I wouldn't be bothering with it if I didn't need it.

And, Tom - you're right, seeing a subfile fill or array values initialized 
in a DO/FOR loop is a waste.  Fortunately for me, there aren't any 
subfiles, the DO loops are limited, and processing that takes place in 
them does need to be tracked.


-- 
David Schopp
WISDM Team Leader
Computers Unlimited