On the slides in the PROFILER presentation, the statistics for the two END statements are different. Why is that?
END statements may show variation in CPU times because activities that occur during the execution of an END statement are very complicated. The time an END statement takes depends on activities that are external to the program, such as NATURAL housekeeping activities, including popping stacks and restructuring/relocating local data areas, and NATURAL Buffer Pool activities, such as searching for the next program, loading the next program, and initializing the next program. PROFILER does not stop measuring CPU time for the END statement until the first executable statement of the next program is encountered.
