§ Use Quantify and its command-line options with your test harness and scripts. Profile your nightly build and check the results the next morning.
§ Settings and preferences you set in the Quantify user interface are recorded as options in the configuration settings (.ini) files for Quantify and for your program, and are applied when you use Quantify from the command line.
§ Limit instrumentation to just a few classes or modules by using the selective instrumentation feature. Use the /ClassInstrumentationType or the /SelectiveInstrumentation command line option.
§ Make your scripts run the instrumented version of your native-compiled program and collect performance data for every run. To do this, specify the /replace option when you instrument. This option renames your program and replaces it with the instrumented version.
§ Apply filters from the command line. Use the /FilterFiles option to specify the filters you want.
§ You can control how functions are measured when you profile programs from the command line or using a test script. For example, specify the /QuantifyLineMust option to collect data at line level.
Note:
§ If you are using Microsoft Windows 2000 or higher, the Windows File Protection feature (WFP) may cause problems when you use the /replace option. For a workaround to this problem, click .
(C) Copyright IBM Corporation 1993, 2009.