PE Benchmarker consists of the Performance Collection Tool
ppe.perf fileset and the Profile Visualization Tool
ppe.pvt fileset. In addition, if
ppe.perf is installed, ppe.dpcl must also be
installed. Installing PE Benchmarker
creates the directories and files detailed in the following table:
Table 6. ppe.perf and ppe.pvt directories and files installed
| Directory or File | Description |
|---|---|
| /usr/lpp/ppe.perf/READMES | Directory containing necessary files to be read by the customer |
| /usr/lpp/ppe.perf/bin | Directory containing executables |
| /usr/lpp/ppe.perf/config | Directory containing configuration files PCT uses to determine hardware counter groups |
| /usr/lpp/ppe.perf/deinstl | Directory containing packaging information for uninstalling the product |
| /usr/lpp/ppe.perf/help | Directory containing help images and files |
| /usr/lpp/ppe.perf/lib | Directory containing libraries used by PCT |
| /usr/lpp/ppe.perf/resources | Directory containing JAVA resource bundles used for labelled text in graphical user interface |
| /usr/lpp/ppe.perf/samples | Directory containing sample programs and scripts |
| /usr/lpp/ppe.perf | Directory containing the necessary Performance Collection Tool files. |
| /usr/lpp/ppe.pvt | Directory containing the necessary Profile Visualization Tool files. |
In addition, symbolic links set up for PE Benchmarker files and libraries are placed in the following directories.
If you install the ppe.perf fileset, you must also install the ppe.dpcl fileset. You need superuser (root) authority to install DPCL. If you plan to use tools built using DPCL with more than one node, you must install DPCL on all of the nodes you want to use. You can do this by making the same image available to the other nodes, either by copying or mounting the image file, then using installp to install the image. You can also set up a host list file and run installp via dsh (for SP systems only) or rsh, and install the DPCL filesets on multiple nodes simultaneously.
Table 7. DPCL directories and files installed
| Directory or File | Description |
|---|---|
| /usr/lpp/ppe.dpcl/bin | Directory containing DPCL |
| /usr/lpp/ppe.dpcl/bin/dpcld | DPCL daemon |
| /usr/lpp/ppe.dpcl/bin/dpclSD | DPCL super daemon |
| /usr/lpp/ppe.dpcl/include | Directory containing the class library header files |
| /usr/lpp/ppe.dpcl/lib | Directory containing the DPCL libraries |
| /usr/lpp/ppe.dpcl/lib/libdpcl.a | Library for building tools |
| /usr/lpp/ppe.dpcl/lib/dpcl_afs.o | Dynamic library used by DPCL in AFS configurations |
| /usr/lpp/ppe.dpcl/READMES/dpcl.README | Installation README file |
| /usr/lpp/ppe.dpcl/samples | Directory containing sample tools that use DPCL |
| This link: | To: |
|---|---|
| /etc/dpcld | /usr/etc/dpcld |
| /etc/dpclSD | /usr/etc/dpclSD |
| /usr/etc/dpcld | /usr/lpp/ppe.dpcl/bin/dpcld |
| /usr/etc/dpclSD | /usr/lpp/ppe.dpcl/bin/dpclSD |
| /usr/lib/libdpcl.a | /usr/lpp/ppe.dpcl/lib/libdpcl.a |
Also, as part of the post-installation steps, the following steps occur.
If no entry for the dpclSD service is found, an entry is added.
If an entry exists for the dpclSD service, no change is made to the /etc/inetd.conf file.