Code Profiling Utilities Manual

Converting Raw Data Files to DPI Files
HP Code Profiling Utilities Manual542684-003
5-3
Saving DPI Files from Previous Runs
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 in the Windows and OSS environments, and pgodpi in the
Guardian environment.)
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 optimizations or
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 have changed the source code since those
runs. The profmrg tool does not verify that its input files reflect the same source code
versions.
Where to Put the Input Files
The profmrg utility looks for all the input files and creates the output file relative to
some directory or subvolume. By default, profmrg uses the current working directory
(OSS and Windows environments) or the default subvolume (Guardian environment),
but you can change the location with the -prof_dir option of the profmrg command,
as described in Run profmrg.
The profmrg utility automatically uses these files as input:
On the workstation, any file whose name has the form ZZPF* or *.dyn.
In an OSS directory on the NonStop server, any file whose name has the form
*.dyn.
In a Guardian subvolume on the NonStop server, any file whose name has the
form ZZZPF*.
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.