Code Coverage Tool Reference Manual

Converting Raw Data Files to DPI Files
HP Code Coverage Tool Reference Manual for HP Integrity NonStop NS-Series Servers—542684-004
5-2
Assembling Raw Data Files
The meaningfulness of the code coverage report depends on the consistency of the
SPI file, the DPI file, and the source files provided as input. Specifically, for the results
of a study to be meaningful, all inputs should reflect the same versions of the source
files. The profmrg utility performs no validation in this regard.
Assembling Raw Data Files
Names of raw data files have one of two possible forms:

ZZPF* if the program was run in the Guardian environment, or if the program was
run in the OSS environment and the current directory is a Guardian subvolume

*.dyn if the program was run in the OSS environment and the current directory is
an OSS directory
To use raw data files as input to profmrg, you must first use FTP or some other
mechanism to copy the files from the NonStop server to the workstation where profmrg
will run.
Saving DPI Files from Previous Runs
If you want to save the file generated by a previous version of profmrg, to prevent the
tool from replacing the existing file, you can:

Move the existing file to a different location, or rename it. (The default name for the
DPI file is pgopti.dpi.)

Use the -prof_dpi runtime option, described in Run profmrg, to specify a name
for the new DPI file
If a file of the same name as the output file already exists, profmrg displays a warning
message on the standard error file and replaces the file. If the file is specified for the
-a option, it is used as an input DPI file.
For additional considerations, see The Output DPI File
.
Including DPI Files from Previous Runs
You can submit DPI files from previous profmrg runs, to base your code coverage
analysis on cumulative data. The -a runtime option, described in Run profmrg
, lets you
specify the set of DPI files to use as input.
Do not use files from previous runs if you’ve changed the source code since those
runs. The profmrg tool does not verify that its input files reflect the same source code
versions.
Note. If you plan to use the -a option to specify the set of DPI files to use, be sure to verify in
advance that each of those files exists.