Measuring Selected Coding Extracts 
Measuring Selected Coding Extracts
Use
You can also start the runtime analysis for a selected coding extract, which is not selected dynamically via breakpoints until runtime. This is a useful alternative to code measurements with
SET RUN TIME ANALYZER ON and SET RUN TIME ANALYZER OFF because the source code does not need to be changed.
Prerequisites
When you specify the coding extract, it is important that the entry and exit point are at the same level, otherwise the results will be incomplete. The start and end of a form routine, function module, method or an event block are at the same level. The start and end of a branch and a loop are also at the same level.
Before you start the runtime analysis for selected coding extracts, you have to choose Change in the measurement restrictions field group in the initial screen to select
Particular units in the next screen. You also have to restrict the coding extract to be measured using two breakpoints. These can be static or dynamic.
Procedure
When the first breakpoint set in the source code is reached, you can start the runtime analysis by choosing the appropriate menu path or via the command field. Proceed as follows:
Choose |
System ? Utilities ? Runtime analysis ? Switch On |
|
System ? Utilities ? Runtime analysis ? Switch Off | |
Transaction code |
/RON <Return> |
|
/ROFF <Return> |
If you then press F8, all the statements up to the second breakpoint are executed and measured. Finally, you have to switch off the runtime analysis by choosing the appropriate menu path or via the command field (see table above).
Result
The results are made available in the same way as for other measurements in the form of measurement overviews and hit lists. The results also contain time values of the Debugger, which can be identified from the program names.