Code Profiling Utilities Manual

Running the Code Cover Utility

HP Code Profiling Utilities Manual—542684-003

7-2

Prepare to Run codecov

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 codecov utility performs no validation in this regard.

Providing for Source File Retrieval

You need not specify source file names explicitly to the codecov utility, because the

files are listed in the SPI and DPI files. You must, however, ensure that the files are in

the locations reflected in the SPI and DPI files and are accessible on disk or over the

network.

Part of the function of codecov is to retrieve and examine the source files to be

included in the analysis, wherever those source files happen to be. The filename listed

in a SPI or DPI file indicates to codecov whether the source file is on the Guardian,

OSS, or Windows platform. If a source file name found in the SPI file is a Guardian or

OSS file name, codecov uses an FTP session to fetch a copy of the source file to the

workstation. To enable this behavior, you specify the -host and -login options on

the codecov command line. You may also specify the -passwd option to provide the

password in advance; otherwise, you will be prompted (on the standard output file) to

type the password (on the standard input file.) The password must be the one

associated with the name specified in the -login option. For security reasons,

codecov does not echo the password when you type it.

You can have a mix of source files:

•

On different NonStop servers in the same network

•

In the Guardian or OSS environment

•

On the workstation where codecov is running

However, all source files fetched from the NonStop server must be in the same

network as the machine specified with the -host option. Also, Guardian source files

must be of code 101 or 180. Be sure to set up any required permissions or remote

passwords to allow codecov access to your source files.

If codecov is unable to fetch a particular source file, it writes a warning message, and

the code coverage report excludes data about that file.