NAME
pct - Invokes the Performance Collection Tool (PCT) in either its graphical-user-interface or command-line mode.
SYNOPSIS
pct [-c [-s script_file]]
The pct command starts the PCT in either its graphical-user-interface mode, or, if the -c flag is specified, its command-line mode.
FLAGS
DESCRIPTION
The PCT is a highly scalable performance monitoring tool built on dynamic instrumentation technology -- the Dynamic Probe Class Library (DPCL). Using the PCT, you can collect:
or
Since the MPI and user trace information will be output as standard AIX trace files, we have also supplied, as part of the PE Benchmarker tool set, several utilities for converting the AIX trace files created by the PCT into a format readable by Jumpshot and the utestats utility.
The PCT can be run in either its graphical-user-interface mode, or, if the -c flag is specified, its command-line mode. The PCT's graphical user interface is built on top of its command-line interface; in other words, your manipulations of the graphical user interface are translated by the tool into pct subcommands. These subcommands are issued, and the information returned is used to update the graphical user interface. The pct subcommands that result from your interface interactions are displayed in an information area of the PCT's Main Window.
When running in command-line mode, you can optionally have the PCT read its commands from a script file. You can specify the script file using the -s option when issuing the pct command, or you can use the run subcommand.
The pct command's subcommands (for controlling the PCT in command-line mode) are listed alphabetically under Subcommands of the pct command.
EXAMPLES
To start the PCT in graphical-user-interface mode:
pct
To start the PCT in command-line mode:
pct -c
To start the PCT in command-line mode, and read commands from the script file myscript.cmd.
pct -c -s myscript.cmd
RELATED INFORMATION
Commands: uteconvert(1), pvt(1), slogmerge(1), utemerge(1), utestats(1)