–o outputfile[,appendcreate]

--rule-files rulefile1[,rulefile2,...]

For these options:

 

--advice-classes

Specifies which classes of advice are printed. It can be all or any

 

combination of general, cpu, memory, io, or system, separated

 

by colons (:).

 

The default is all.

--advice-cutoff

Specifies how much of the advice to print. All advice is sorted by its

 

index value (the greater the index, the greater the importance).

 

min-indexspecifies the lowest index value of advice to print.

 

min-countgives the minimum number of advice items to print while

 

max-countgives the maximum number. min-counttakes precedence

 

over min-index, so if only a few pieces of advice apply, some with

 

an index less than min-indexmight be printed.

 

The defaults are 5.0 for min-index, 5 for min-count, and 15 for

 

max-count.

--advice-details

Specifies what portions of advice messages are printed. It can be all

 

or any combination of description, improvement, measurement,

 

explanation, or rule, separated by colons (:). Advice messages

 

don’t necessarily contain all of these portions.

 

The default is all.

--analysis-focus

Specifies which application object(s) to analyze and report on. Currently,

 

only executable programs can be analyzed, so specifying the default

 

focus type of executable is optional. The object name can be all

 

or a specific, simple executable name such as my_app. One or more

 

executables can be specified with this option, separated by commas

 

(,).

 

The default is executable:all.

-o

Specifies the name of the report file produced by the Advisor. The report

 

file is in text format. The Advisor will either create a new file (create)

 

or append to an existing file (append).

 

The default file is stdout and the default action is create.

 

Can also be specified as --output-fileoutputfile.

--rule-files

Specifies the name or names of existing rule files to use for the analysis.

 

One or more rule files can be given, separated by commas (,). A rule

 

file can be a customized rule file in your own personal rules directory

 

or a standard HP Caliper rule file in the HP Caliper directory. A rule file

 

can be either a simple filename or a relative or absolute path name.

 

For a simple filename, directories are searched in this order: (1) the

 

current directory, (2) the personal rules directory ~/caliper_advisor,

 

and (3) the rules subdirectory in the HP Caliper home directory.

 

For a relative or absolute path name, no searching is done.

database_list is a set of one or more HP Caliper databases to analyze. If the databases are specified by name (with or without a path), they are looked for at those locations. If they are specified only by name, they are looked for in these locations, in this order: (1) current directory, then (2) databases directory. If no databases are specified by name, all the databases in the databases directory are analyzed.

For information about what the options mean, see “How to Read an Advisor Report” (p. 83).

80 Using the HP Caliper Advisor