images\quantify_sml.gifimages\coverage_sml.gif instrumentation state

For native-compiled applications using selective instrumentation, a setting that indicates the level of persistence of an instrumented module:

§      Transient: an instrumented copy temporarily replaces the original module for the duration of the program run. When your program exits, the original, uninstrumented module is restored.

§      Permanent: an instrumented copy replaces the original, uninstrumented module until you manually change the module's instrumentation state. The original, uninstrumented module is not restored after your program exits.

§      None: the original, uninstrumented module is used for all program runs.

Selective instrumentation states are supported for native-compiled (unmanaged) code only.

Notes:

§      Even when you are not running programs in Rational Runtime Analysis tools, a call to a native-compiled module in the permanent instrumentation state will cause the Runtime Analysis tool that instrumented it to load and begin collecting data for the module.

§      When you instrument a module such as a .dll or an ActiveX control in the transient state, analysis data is collected the first time you load and execute the module. If your program unloads the module and then reloads it during the same program run, data will not be collected for the subsequent execution. To collect data for a module each time you reload it during a program run, instrument the module in the permanent state.

See also selective instrumentation in the glossary.

(C) Copyright IBM Corporation 1992, 2010.