HP UX Web Development Tools manual PDB options table, Specifying the PDB location, Deleting PDB

3.1 PDB options table

The following options help you manage the PDB:

“-pdb location” (page 20)

“-pdb_destroy” (page 20)

“-pdb_no_locking” (page 20)

“-remove” (page 20)

“-snapshot location” (page 21) “-pdb_version” (page 21)

Enables you to specify the location (path) of the PDB.

Removes the PDB specified with the –pdb option.

Allows you to not to use locks in PDB operations.

Removes information related to the specified object files from the PDB.

Creates a snapshot of the PDB at the specified location (path). Prints the PDB version and checks for compatibility.

3.2 Specifying the PDB location

The path specified may be relative or absolute, but you must ensure that the whole application build creates only one PDB. If the build of your application is done across multiple machines, you must ensure that the path specified is accessible from all the machines involved in creating the build.

Following is the syntax for changing the location of the PDB:

$cadvise <location> -pdb <pdbname>

Following is an example to specify the location of the PDB:

Example 6 Specifying the PDB Location

$cadvise -pdb testpdb /opt/aCC/bin/aCC 1.c

Where: testpdb is the location of the PDB.

3.3 Deleting PDB

This option enables you to delete the PDB when it is no longer required.

Following is the syntax for deleting PDB:

$cadvise -pdb_destroy -pdb <pdbname>

Following is an example to delete the PDB:

Example 7 Destroying PDB

$cadvise -pdb_destroy -pdb testpdb

Where: testpdb is the location of the pdb, to be deleted.

3.4 Disabling locks in PDB operations

The -pdb_no_lockingoption ensures that cadvise does not use locks in PDB operations. Cadvise uses locks implemented with lockf during some PDB operations, by default. If the user machine does not use lockd, or if there are any name resolution issues between the PDB host and client machines, the lockf calls do not execute for an indefinite period of time. Use the -pdb_no_lockingoption to workaround lockf related-issues in user systems. Locks are important if the user has to run cadvise analysis and reports simultaneously. If you do not use locks and run cadvise analysis in parallel with the reports, then there is a potential for incomplete or truncated reports. See also : manpages on lockf(2); lockd(1M).

3.5 Removing object file information from the PDB

The -removeoption removes from the PDB, any information such as logs, internal representation, and metrics related to the specified object files.

20 Using the Program Database (PDB)