images\purify_sml.gifimages\quantify_sml.gifimages\coverage_sml.gifinstrumentation

The process of inserting additional code into a compiled program and each associated module or class, for the purpose of collecting measurement data as the program runs.

Depending on how your program was compiled, Rational Runtime Analysis tools use one of the following:

§    For native-compiled (unmanaged) executables, Object Code Insertion (OCI) technology is used. By default, instrumented copies of modules are saved and executed from a cache directory. If a program or module is not modified between application runs, the saved instrumented version is reused.

§          For Java, .NET, and Visual Basic p-code, Byte Code Insertion (BCI) technology is used. BCI instrumentation is performed dynamically in memory for each run of an application, the instrumented files are not saved between runs.

There are two modes of instrumentation:

§          Inclusive: all modules or classes that you do not specifically exclude are instrumented. Inclusive instrumentation is the default.

§          Selective: only the modules or classes you select are instrumented; all others are excluded.

Rational Runtime Analysis tools provide various instrumentation level settings that you can use to customize and fine tune data collection. The level of instrumentation actually performed is dependent upon the availability of debug and relocation data.

See also Object Code Insertion (OCI), Byte Code Insertion (BCI), and instrumentation mode in the glossary.

(C) Copyright IBM Corporation 1993, 2009.