Format

@file-spec

The @file-spec command reads and executes the commands contained in the specified command procedure as if the commands were entered at the terminal. The command procedure can contain any valid PCA commands, including other @file-spec commands.

When PCA executes an EXIT command in the command procedure or reaches the end of the file, it returns control to the command stream that invoked the command procedure. That command stream can be the terminal or a previous command procedure. Command procedure nesting is limited to 16 levels.

If you enter the SET VERIFY command, all commands read from the command procedure echo on the terminal.

Example

PCAC> @CMD_FILE.PCAC

This command reads Collector commands from the file CMD_FILE.PCAC until an EXIT command is encountered or the end-of-file is reached.

Format

APPEND [file-spec]

The APPEND Analyzer command concatenates many separate histograms, tables, or listings into a single file. You can specify a file, or accept the most recently created file as the default; however, the file must exist.

Example

PCAA> TABULATE/SOURCE PROGRAM BY LINE
PCAA> APPEND [MYDIR]FOOLINES.PCALIS
%PCA-I-APPFILE, appending to file DEV$:[MYDIR]FOOLINES.PCALIS

A table is generated with the TABULATE command. That table is then appended to the existing text file FOOLINES.PCALIS in directory [MYDIR].

Format

ATTACH process-name

The ATTACH command connects your terminal to another process. Using the ATTACH command, you can switch control back and forth between several different active processes. To create additional processes, use the SPAWN command from within PCA or at the DCL level.

Example

PCAC> SPAWN
            ! Spawn subprocess NICK_1
$ TYPE FOO.DAT
         ! Enter DCL commands in subprocess
text line in foo.dat
$ ATTACH NICK
          ! Attach to original process
%PCA-I-RETURNED, control returned to process NICK
PCAC> SHOW LANGUAGE
    ! Enter Collector commands
Language: PASCAL
PCAC> ATTACH NICK_1
    ! Attach back to subprocess
%PCA-I-ATTACHED, terminal now attached to process NICK_1
$ 

In this example, the Collector SPAWN command creates a subprocess. DCL commands are executed in the subprocess. A DCL ATTACH command reattaches the terminal to the Collector session. The Collector session continues with additional Collector commands until a Collector ATTACH command is entered to reconnect the terminal to the subprocess.

Format

BACK [subtree]

The BACK Analyzer command enables you to traverse a program's structure. The BACK command displays the current plot and positions an arrow to point to the bucket with the next highest number of data points (the previous leaf). The corresponding source lines for that portion of the program are displayed beside the plot. Other traverse commands are FIRST, NEXT, and CURRENT.

Format

CANCEL keyword [parameters]

CANCEL is not an individual command. Each CANCEL command consists of the word CANCEL followed by a required keyword. See the descriptions of the individual CANCEL commands for details.

Format

CANCEL ALL

On OpenVMS Alpha and OpenVMS VAX systems, the CANCEL ALL Collector command cancels all data collection options established with the following SET commands:

In addition, the AST timer is reset to 10, the default.

Format

Format

CANCEL COUNTERS [nodespec, [nodespec...]]

The CANCEL COUNTERS Collector command cancels execution counters at the program locations specified by the node specification, or the /ALL qualifier. If you first set an execution counter at a program location with SET COUNTERS and then cancel it with CANCEL COUNTERS, no execution count is measured at that location when the GO command is entered.

Examples

Format

CANCEL COVERAGE [nodespec [,nodespec...]]

The CANCEL COVERAGE Collector command cancels the collection of test coverage data at the program locations specified by the node specification, or by the /ALL or /PREVIOUS qualifiers. If you first establish test coverage measurement at a program location with SET COVERAGE and then cancel it with CANCEL COVERAGE, no data is gathered at that location when the GO command is entered.

Examples

Format

CANCEL CPU_SAMPLING

The CANCEL CPU_SAMPLING Collector command disables the collection of CPU sampling data established with an earlier SET CPU_SAMPLING command.

Format

CANCEL DATAFILE

The CANCEL DATAFILE command closes the current performance data file. The Collector does not record data in that file when data collection starts. Instead, it uses the default data file, or the data file you establish with a subsequent SET DATAFILE command. The Analyzer does not read or process data until another SET DATAFILE command is entered.

Format

CANCEL DISPLAY [display-name [,display-name...]]

The CANCEL DISPLAY command cancels the specified screen displays. When a screen display is canceled, it disappears from the screen and its contents and definition are permanently lost.

Format

CANCEL EVENT [event-name [nodespec [,nodespec...]]]

The CANCEL EVENT Collector command cancels the collection of event markers for a specified event when the node specifications associated with that event are executed. Event markers for the event-name event are not recorded in the performance data file when these program locations are executed. If you specify an event name without a node specification, all node specifications associated with the event name are canceled.

Examples

Format

CANCEL FILTER [filter-name [,filter-name...]]

The CANCEL FILTER Analyzer command deletes the specified filters so they no longer filter the performance or coverage data used by the PLOT and TABULATE commands. Filters specify which data points from the performance data file to tally in histograms and tables.

Format

CANCEL IO_SERVICES

The CANCEL IO_SERVICES Collector command disables the collection of I/O services data established with an earlier SET IO_SERVICES command.

Format

CANCEL LOG

The CANCEL LOG command disables the recording of input and output in a log file. This command cancels the effect of an earlier SET LOG command.

Format

CANCEL PAGE_FAULTS

The CANCEL PAGE_FAULTS Collector command disables the collection of page-fault data established with an earlier SET PAGE_FAULTS command.

Format

CANCEL PC_SAMPLING

The CANCEL PC_SAMPLING Collector command disables the collection of program counter sampling data established with an earlier SET PC_SAMPLING command.

Format

CANCEL PLOT

The CANCEL PLOT Analyzer command sets the SET PLOT default qualifiers to their initial values and sets the default node specification to PROGRAM_ADDRESS BY ROUTINE. The SET PLOT defaults are set with the SET PLOT command and specify qualifier defaults for the PLOT and TABULATE commands that have node specifications. (PLOT and TABULATE commands without node specifications take their defaults from the currently active plot.) The SET PLOT defaults also specify all qualifier and node specification defaults for PLOT and TABULATE commands that have the /DEFAULT qualifier.

Format

CANCEL SERVICES

The CANCEL SERVICES Collector command disables the collection of system services data established with an earlier SET SERVICES command.

Format

CANCEL SOURCE

The CANCEL SOURCE command cancels the source-file directory search list established with a previous SET SOURCE command. After the directory search list is canceled, the Collector cannot find any source file that has been moved or copied since being compiled.

If you have established a directory search list for a specific module with the SET SOURCE/MODULE=module-name command, you must use the same /MODULE qualifier on the CANCEL SOURCE command to cancel that search list.

If you have established a directory search list for the EDIT command using the SET SOURCE/EDIT command, you must use the same /EDIT qualifier on the CANCEL SOURCE command to cancel that search list.

Format

CANCEL STACK_PCS

The CANCEL STACK_PCS Collector command disables the collection of call stack PC values. It cancels the effect of an earlier SET STACK_PCS command.

Format

CANCEL TASKING

The CANCEL TASKING Collector command disables the collection of tasking data established with a previous SET TASKING command.

Format

CANCEL TITLE

The CANCEL TITLE Analyzer command deletes the title text established with the previous SETTITLE command. Instead, the following default title text appears on each page of PLOT or TABULATE output:

            HP Performance and Coverage Analyzer

Format

CANCEL UNALIGNED

Example

PCAC> CANCEL UNALIGNED

This example disables the collection of unaligned access fault data.

Format

CANCEL VCOUNTERS [nodespec, [nodespec...]]

The CANCEL VCOUNTERS Collector command cancels vector instruction counters at the program locations specified by the node specification, or by the /ALL qualifier. If you first set a vector instruction counter at a program location with SET VCOUNTERS and then cancel it with CANCEL VCOUNTERS, no execution count is measured at that location when the GO command is entered.

Examples

Format

CANCEL VCPU_SAMPLING

The CANCEL VCPU_SAMPLING Collector command disables the collection of vector CPU sampling data established with an earlier SET VCPU_SAMPLING command.

Format

CANCEL VERIFY

The CANCEL VERIFY command disables the echoing of command input to the terminal established with an earlier SET VERIFY command.

Format

CANCEL VPC_SAMPLING

The CANCEL VPC_SAMPLING Collector command disables the collection of vector PC sampling data established with an earlier SET VPC_SAMPLING command.

Format

CANCEL WINDOW [window-name [,window-name...]]

The CANCEL WINDOW command cancels the specified screen window definitions. After a window definition has been canceled, that window name can no longer be used on DISPLAY or SET DISPLAY commands. Only the definition of the window name is deleted; the actual screen region specified by the window name is not affected. Screen displays declared with the window name are not affected; however, the SHOW DISPLAY command shows numeric window coordinates for such windows instead of the canceled window name.

Format

CURRENT [subtree]

The CURRENT Analyzer command allows you to traverse a program's structure. The CURRENT command displays the current plot with the pointer and corresponding source lines in the same position. The corresponding source lines for that portion of the program are displayed beside the plot.

The CURRENT SUBTREE command displays the current subtree at its first leaf (which is equivalent to the FIRST command). Other traverse commands are FIRST, NEXT, and BACK.

Format

DEFINE/COMMAND symbol-name = "command-string"

The DEFINE/COMMAND command associates a symbol name with a PCA command string. The command string consists of one or more PCA commands separated by semicolons, and must end with a partial or full PCA command. When the symbol name appears at the start of a subsequent PCA command, it is replaced by the command string. The resulting string is parsed and executed by PCA. DEFINE/COMMAND gives you the same command abbreviation capability as the symbol assignment statement (symbol-name := command-string) in DCL. The command string can contain previously defined commands when those symbols translate directly into PCA commands. (PCA supports one level of symbol translation.)

To display the current symbol definitions created by DEFINE/COMMAND, use the SHOW SYMBOL/DEFINED command.

Example

PCAC> DEFINE/COMMAND SA = "SHOW ALL"
PCAC> SA

This command associates the symbol SA with the PCA command SHOW ALL. When the SA command is used, SA is expanded to the equivalent command string, which PCA then executes.

Format

DEFINE/KEY key-name "command-string"

The DEFINE/KEY command assigns PCA command strings to keypad keys. When you press the appropriate keypad key, PCA enters the associated command string into your command line.

The key definition remains in effect until you redefine the key (by entering another DEFINE/KEY command for the same key), enter the DELETE/KEY command for that key, or exit. You can include key definitions in a command procedure, such as your PCA initialization file.

Example

PCAC> DEFINE/KEY/TERMINATE KP7 "SHOW ALL/FULL"

This command associates KP7 with the SHOW ALL/FULL command. Because the /TERMINATE qualifier is used, you do not need to press the Return key after pressing KP7 to execute the command.

Format

DELETE/COMMAND symbol-name [, symbol-name...]

Example

PCAC> DELETE/COMMAND FOO, FEE

This example deletes the command definitions for symbols FOO and FEE.

Format

DELETE/KEY key-name

Example

PCAC> DELETE/KEY KP7

This command deletes the key definitions for KP7.

Format

DISPLAY [display-name [AT window-spec] [display-kind]

[, display-name [AT window-spec] [display-kind]...]]

DISPLAY/REFRESH

The DISPLAY command shows the contents of the specified screen displays. Each specified display is placed on top of any other displays that occupy overlapping windows on the screen.

You can also use the DISPLAY command to change the attributes of the specified screen displays. You can create displays that do not appear on the screen, change their sizes, clear their contents, and change their window locations and display kinds.

Examples

Format

EDIT [[module-name \] line-number]

The EDIT Analyzer command invokes an editor to edit the source file displayed by the current PLOT or TABULATE command. To get a source display, use the /SOURCE qualifier on the PLOT or TABULATE command and use a BY LINE or BY CODEPATH node specification.

If you do not specify a parameter on the EDIT command, the editor is positioned at the central line of the page currently shown on your terminal. The module-name and line-number parameters enable you to position the editor at a different source file or line.

When you exit from the editor, you are returned to the Analyzer session. However, if you use the /EXIT qualifier on the EDIT command, the Analyzer session is terminated before the editor is invoked.

The editor you call must be accessible from DCL level, and can be set with the SET EDITOR command. For more information, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Format

EXCLUDE n

The EXCLUDE Analyzer command removes one datakind from a multiple datakind plot. Multiple datakind plots are created by the INCLUDE command. The EXCLUDE command provides an incremental approach to building a plot or table. After you execute this command, a new plot or table is created and displayed. For complete information about multiple datakinds, see the Guide to VSI DECset Performance and Coverage Analyzer for OpenVMS Systems.

Example

PCAA> EXCLUDE 6

This command creates, then displays, a new plot or table that excludes the sixth datakind.

Format

EXIT

When you enter the EXIT command at the terminal, the session ends and you return to DCL level. You can also press Ctrl/Z to end the session.

When PCA executes an EXIT command in a command procedure, control returns to the command stream that invoked the command procedure. This command stream can be the terminal or a previous command procedure. To return to the DCL command level after invoking PCA in a command procedure, define the logical name PCAA$INPUT to be a file that contains an EXIT command. PCA executes the PCAA$INIT command file at invocation and then gets its input from the PCAA$INPUT file. Because the PCAA$INPUT file has an EXIT command, you will then exit PCA.

Format

EXPAND [disp-name[, . . . ]]

The EXPAND command moves one or more display-window borders according to the qualifiers specified. You must specify at least one qualifier.

The EXPAND command does not affect the order of a display on the display pasteboard. Depending on the relative order of displays, the EXPAND command might cause the specified display to hide or uncover another display, or be hidden by another display, partially or totally.

Except for the PROMPT display, any display can be contracted to the point where it disappears (at which point it is marked as removed). It can then be expanded from that point. Contracting a display to the point where it disappears will cause it to lose any attributes that were selected for it. The PROMPT display cannot be contracted or expanded horizontally, but can be contracted vertically to a height of two lines.

A window border can be expanded only up to the edge of the screen. The left and top window borders cannot be expanded beyond the left and top edges of the display, respectively. The right border can be expanded up to 255 columns from the left display edge. The bottom border of a display can be expanded down only to the bottom edge of the display (to the end of the source module or routine's instructions).

Examples

Format

EXTRACT [disp-name[, . . . ]] [file-spec]

When you use the EXTRACT command to save the contents of a display into a file, only those lines that are currently stored in the display's memory buffer (as determined by the /SIZE qualifier on the DISPLAY or SET DISPLAY command) are written to the file.

You cannot extract the contents of the PROMPT display into a file.

Examples

Format

FILE file-spec

The FILE Analyzer command writes the output to a file. To write a histogram, table, or listing of raw performance data to a file, enter a command to generate the report on the terminal, then enter a FILE command to write that report to a file. The text file can be printed or used as input to other programs.

When writing histograms and tables to a file, the FILE command assumes that there are 66 lines per page and formats the output accordingly. You can change the number of lines per page by defining the logical name SYS$LP_LINES at DCL level.

You can concatenate many separate histograms, tables, or listings into a single file by using the /APPEND qualifier or APPEND command.

Examples

Format

FIND [label-name]

The FIND Analyzer command finds the first page of histogram or table output that contains a specified label and displays that page on the terminal. It is useful for quickly finding specific bucket names in long histograms or tables.

Examples

Format

FIRST [subtree]

The FIRST Analyzer command allows you to traverse a program's structure. This command displays the current traverse subtree and positions an arrow to point to the bucket with the most data points. The corresponding source lines for that portion of the program are displayed beside the plot. Other traverse commands are NEXT, BACK, and CURRENT.

Format

GO

The GO Collector command executes a program and collects performance or coverage data while the program runs to completion. After entering the GO command, you cannot enter more Collector commands.

If you do not establish a performance data file with the SET DATAFILE command before entering the GO command, the Collector uses a default data file. The default data file has the same file name as your program's executable image file and a file type of .PCA. If you do not establish any data collection options before entering the GO command, the Collector gathers program counter sampling data and stack data by default.

Format

HELP [topic [subtopic...]]

If you want information about a particular qualifier or parameter, specify it as a subtopic. If you want information about all command qualifiers, specify “Qualifier” as a subtopic. If you want information about all parameters, specify “Parameter” as a subtopic. If you want all available information about a command, specify an asterisk (*) as a subtopic. If you want to redisplay the last help entry you viewed, enter a question mark (?).

Format

INCLUDE

The INCLUDE Analyzer command adds a new datakind into the current plot. It is used with the EXCLUDE command to incrementally build one plot that contains a maximum of eight datakinds per bucket. The datakinds must be compatible with the node specifications for the current plot. If you want a new set or order of the buckets, you must enter a new PLOT or TABULATE command. The use of INCLUDE command qualifiers does not affect the old qualifiers in the PLOT/TABULATE default entry of the current active plot. If no active plot is available, an error message is displayed. You can apply a different filter to the datakind for every INCLUDE command. The first page of the newly created plot is displayed after you enter the command.

For more information on multiple datakinds, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Example

PCAA> PLOT/MAIN_IMAGE/IO_SERVICES/FILL=("io","pc") PROGRAM BY ROUTINE
PCAA> INCLUDE/PC_SAMPLING
PCAA> INCLUDE/PHYSICAL_IO/FILL="phys_io"

              HP Performance and Coverage Analyzer                 Page 1
         I/O System Service Calls (316152 data points total) - "io"
      Program Counter Sampling Data (1019612 data points total) - "pc"
         Total Physical I/O Counts (206391 data points total) - "phys_io"
Bucket Name         +----+----+----+----+----+----+----+----+----+----+
INPUT_DATA\         |
 INPUT_DATA . . . . |ioioioioioioioioioioioioioioioioioioioiioioio  79.1%
                    |pcpcpcp                                        11.9%
                    |p                                              0.1%
SORT_PRIMES\        |
 SORT_PRIMES  . . . |ioioioioi                                      13.9%
                    |pcpcpcpcpcpcpcpcpcpcpcpcpcpcpcpcpcpcpcpcpcpc   83.7%
                    |phys_iophys_iophys_iophys_iophys_iophys_iophy  99.8%
OUTPUT_PRIMES\      |
 OUTPUT_PRIMES  . . |ioio                                            7.0%
                    |pc                                              3.1%
                    |                                                0.0%
PCA$PRIMES_1\       |
 PCA$PRIMES_1 . . . |                                                0.0%
                    +----+----+----+----+----+----+----+----+----+----+

Format

LIST datakind [,datakind...]

The LIST Analyzer command displays information stored in the performance data file. If you specify datakind parameters, it displays all corresponding performance or coverage data records from the file. Thus, you can inspect the raw performance or coverage data gathered by the Collector. If you specify the appropriate qualifiers, the LIST command displays other information stored in the performance data file (see the qualifier list). You must request at least one kind of information from the LIST command.

PCA can display extensive output from the LIST command. Stop the LIST output by pressing Ctrl/C.

The LIST output can be sent to the printer with the PRINT command, or written to a file with the FILE command. If you write the LIST output to a file, you can use it as input to your own data reduction programs.

Examples

Format

MERGE input-file-spec[,input-file-spec...]

The MERGE command makes it possible for you to combine several PCA performance data files, or to combine data extracted from several SPM data files into one PCA data file. This enables you to process and display the PC sampling data collected by SPM. Merged data is always appended to the currently opened performance data file. For more information on the MERGE command, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Format

MOVE [disp-name[, . . . ]]

For each display specified, the MOVE command creates a window of the same dimensions elsewhere on the screen and maps the display to it, while maintaining the relative position of the text within the window. You must specify at least one qualifier.

The MOVE command does not change the order of a display on the display pasteboard. The MOVE command might cause the display to hide or uncover another display, or be hidden by another display (partially or totally). A display can be moved only up to the edge of the screen.

Examples

Format

NEXT [subtree]

The NEXT Analyzer command enables you to traverse a program's structure. The initial NEXT command displays the first traverse subtree and positions an arrow to point to the bucket with the most data points. The corresponding source lines for that portion of the program are displayed beside the plot. Subsequent NEXT commands move the arrow to the bucket with the next most data points (the next leaf), and so on. Other traverse commands are FIRST, BACK, and CURRENT.

Format

PAGE parameter

The PAGE Analyzer command gives you random access to the pages of the histogram or table generated by the last PLOT, TABULATE, INCLUDE, EXCLUDE, or traverse command you entered. The PAGE command displays the next, current, previous, or first summary page, or a page with a specific page number. You cannot use the PAGE command unless there is a currently active plot or table.

Examples

Format

PLOT [nodespec [,nodespec...]]

The PLOT Analyzer command generates performance or coverage histograms. A number of different kinds of data can be plotted along the horizontal axis, and a variety of data domains can be partitioned into buckets along the vertical axis to form the histogram. For example, the node specification PROGRAM_ADDRESS BY ROUTINE selects the program address domain, the domain of all possible program addresses. From this domain, it selects the address ranges of the routines in the program. Each of these address ranges defines a bucket.

When you enter a PLOT command, you must specify the kinds of data to tally, and the way to partition the histogram. These two things define the meanings of the horizontal and vertical axes of the histogram. What kind of data to tally is specified with a datakind qualifier (see the qualifier list).

Each histogram is partitioned into buckets. Each bucket specifies what each individual histogram bar represents. Each bucket is defined by a value range and corresponds to one histogram bar. Each data point in the data file is tallied in the bucket whose value range includes the value of the data point. For a complete description of node specifications and a listing of Analyzer node specifications, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Every PLOT command requires one qualifier from the datakind and the sorting categories to generate a histogram. If you do not specify one qualifier from each category, a default qualifier is used. If your PLOT command has one or more node specifications, the qualifier defaults are taken from the SET PLOT defaults. If your PLOT command does not have a node specification, all qualifier and node specification defaults are taken from the previous PLOT or TABULATE command you entered.

The TABULATE command displays the same information as the PLOT command, but in the form of tables instead of histograms. For a complete description of the PLOT and TABULATE commands, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Examples

Format

PRINT

To print a histogram, table, or listing of raw performance data, enter the command to generate a report on the terminal, and then enter a PRINT command to send that report to the printer. The print file produced by the PRINT command is named PCAPLOT.TMP and is queued to SYS$PRINT.

When printing histograms and tables, the PRINT command assumes that there are 66 lines per page and formats the output accordingly. You can change the number of lines per page by defining the logical name SYS$LP_LINES at DCL level.

To be notified at your terminal when your output has finished printing, use the /NOTIFY qualifier.

Format

SAVE old-displayname AS new-displayname[,old-displayname AS new-displayname...]

The SAVE command saves a snapshot of an existing screen display in a new display for later reference. The new display has the same textual contents, attributes, and characteristics as the existing display, except it does not appear on the screen. Using the DISPLAY command, you can later recall the saved display to the terminal screen.

Example

PCAA> SAVE PLOT AS SAVED_PLOT

This command moves the contents of the screen display named PLOT into the newly created screen display named SAVED_PLOT.

Format

SCROLL [display-name]

The SCROLL command is used to view display contents that are not currently visible in a display's screen window. Using the SCROLL command, you can move the screen window up or down over the text of the display. You can also move it left or right. By scrolling, you can see all parts of a large display, even though only a small part might fit in the display's window at any one time.

The easiest way to use the SCROLL command is to use the predefined scrolling keys (see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide) on the numeric keypad.

Examples

Format

SEARCH [range] [string]

The SEARCH command enables you to search your source code for a specified string. The source lines containing an occurrence of that string are then displayed. You can use the SEARCH and TYPE commands to display specific lines, or a range of lines. However, if you have moved your source files, you must establish a source directory search list with the SET SOURCE command in order to use these commands. For more information on the SEARCH command, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Example

PCAC> SEARCH/STRING/ALL COBOLTEST "D"\40:50
40: 02    D2N    COMP-2 VALUE -234560000000
41: 02    D      COMP-2 VALUE  222222.33
47: 02    DRO    COMP-2 VALUE  0.1
50: 02    DR5    COMP-2 VALUE  0.000001

This command searches for all occurrences of the letter D in lines 40 through 50 of the module COBOLTEST, and displays the result.

Format

SELECT [display-name]

Attributes are used to select the current scrolling display and direct various types of PCA output to particular displays. This gives you the option of mixing or isolating different types of information, such as PCA input, output, diagnostic messages, and so on, in scrollable displays.

You can use the SELECT command with one or more qualifiers, such as /ERROR or /SOURCE, to assign one or more corresponding attributes to a display. If you do not specify a qualifier, the /SCROLL qualifier is assumed by default.

In general, if you use the SELECT command without specifying a display name, the attribute assignment indicated by the command qualifier is canceled. To reassign display attributes, you must use another SELECT command. See the individual qualifier descriptions in the Parameter and Qualifier Glossary section for details.

Examples

Format

SET keyword [parameters]

SET is not an individual command. Each SET command consists of the word SET followed by a required keyword. For details, see the individual SET command descriptions.

Format

SET ANC [nodespec]

The SET ANC command lets you select particular coverage-set points as acceptably noncovered, and saves that information for the next test run.

There are two ways to specify ANC information. One is to generate a noncoverage or ANC plot or table, then use a traverse command (such as NEXT), or the FIND command, to pinpoint a particular noncovered point. Line the pointer up with the desired bucket, then enter the SET ANC command at the Analyzer prompt. The SET ANC command saves that address as acceptably noncovered. You can continue traversing the plot in this manner until you have saved all the noncovered points. After you enter the first traverse command, you can enter Ctrl/N to move the pointer from one noncovered point to another, or use the KP COMMA to enter the SET ANC command for you.

Another way to save ANC information is to provide a node specification on a SET ANC command, as in the example provided. For complete information about acceptable noncoverage and an example, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Example

PCAA> SET ANC ROUTINE R2 BY LINE, ROUTINE R4 BY LINE

This command saves all noncovered lines in routines R2 and R4 as acceptably noncovered.

Format

SET COUNTERS [nodespec [,nodespec...]]

The SET COUNTERS Collector command establishes execution counters at all program locations specified by the node specifications. After you enter the GO command, the Collector counts the number of times each specified program location is executed and records each execution in the performance data file. Execution counters are implemented with breakpoint instructions.

To place an execution counter at an individual line, you must use the formal name of the corresponding line node. The format is as follows:

LINE [module-name\]%LINE n

In this context, module-name is the name of the module containing the line and n is the line number. You can specify the appropriate routine name instead of the module name as long as the routine name is unique. These path-name qualifications are described in more detail in the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide. The line number is always the compiler-assigned listing line number, which is the same line number the OpenVMS Debugger uses.

Examples

Format

SET COVERAGE [nodespec [,nodespec...]]

The SET COVERAGE Collector command establishes the collection of test coverage data for all program locations specified by node specifications. The Collector places a breakpoint at each specified program location to measure test coverage. After you enter the GO command, the Collector determines whether each specified program location is reached during program execution. When a test coverage breakpoint is reached during program execution, the Collector records that program location in the performance data file. The Collector then removes the breakpoint so the overhead of measuring coverage is not incurred in subsequent executions of the same program location.

If you enter the SET COVERAGE command before entering a SET DATAFILE command, the Collector establishes a default data file. The default data file has the same file name as your program's executable image file and a file type of .PCA.

Examples

Format

SET CPU_SAMPLING

The SET CPU_SAMPLING Collector command enables the collection of PC values based on virtual process or CPU time. When you enter the SET CPU_SAMPLING command, PCA will collect PC values only whenever there has been one or more clock ticks on the process clock.

The Collector places the CPU Sampling AST at an elevated mode to enable the sampling of user mode ASTs.

Examples

PCAC> SET CPU_SAMPLING/INTERVAL=20/NOSTACK_PCS

This command causes the interval to be 20 milliseconds, and disables STACK_PCS collection for this measurement. For all subsequent SET CPU_SAMPLING requests, a default of /NOSTACK_PCS will be assumed.

Format

SET DATAFILE [file-spec]

In the Collector, the SET DATAFILE command identifies the performance data file the Collector should use to record symbol information and performance or coverage data. No performance or coverage data is actually written to the specified file until you enter the GO command. You can specify the data file again with another SET DATAFILE command if you need to correct the data file specification.

If you want to append the data from the present collection run to an existing performance data file, use the /APPEND qualifier. If you want to measure the performance of a shareable image, use the /SHAREABLE qualifier.

In the Analyzer, the SET DATAFILE command identifies a performance data file to be processed by the Analyzer. Data from this file is used by all subsequent PLOT, TABULATE, LIST, and SHOW commands. You can use the SET DATAFILE command to change the performance data file any number of times during the Analyzer session. The Collector builds the performance data file to contain all symbol information and all performance or coverage data required by the Analyzer.

Examples

Format

SET DISPLAY display-name [AT window-spec] [display-kind]

[, display-name [AT window-spec] [display-kind]...]

The SET DISPLAY command creates new screen displays so more displays than the default PLOT, OUT, SRC, and PROMPT displays can appear on your screen. By defining multiple plot displays and selecting each one in turn as the current plot display, you can simultaneously display several different histograms or tables on the screen. Similarly, you can create multiple output displays.

A window in screen mode is a rectangular region on the screen through which you view a display. Its size is defined by a starting line number and by the number of text lines that you want to view through that window.

The screen on a VT-series terminal consists of 24 lines by 80 or 132 columns of text. The screen can also consist of up to 100 lines by 255 columns, depending on the terminal model and the terminal height and width settings.

The pasteboard is similar to a drawing board on the screen to which windows are attached. Each window is pasted onto the pasteboard in the order that it is referenced, and each display is placed in the window with which it is associated. The most recently referenced display is pasted last onto the pasteboard. In addition, as you create more displays, the later displays that you have created might overlay part or all of your earlier displays. What you see on the screen is the final appearance of the pasteboard.

Examples

Format

SET EDITOR [command-line]

The SET EDITOR Analyzer command lets you determine which editor to invoke and how to invoke it when you enter the EDIT command. These editors must be accessible from DCL level. If you do not specify an editor with the SET EDITOR command, the VSI Language Sensitive-Editor is invoked by default. For more information about the SET EDITOR command, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Example

PCAA> SET EDITOR/CALLABLE_LSEDIT/START_POS "LSEDIT/READ_ONLY"

This command causes subsequent EDIT commands to invoke callable LSEDIT with the default command line of LSEDIT/READ_ONLY. The /START_POSITION qualifier will be appended to the command line, which causes the editing session to start on the source line to which the Analyzer is currently pointing.

Format

SET EVENT event-name node-spec[,node-spec . . . ]

The SET EVENT Collector command establishes the collection of event markers for a specified event when you execute program locations associated with that event. An event marker is a data record written to the performance data file to mark that some significant event has occurred during program execution. You determine which events are significant and the names to assign to those events.

When you enter a SET EVENT command, you must specify the name of the event you want to define. You must also specify the node specifications to associate with that event. The Collector places a breakpoint on each location and, when the breakpoint is reached, writes an event marker for that event to the performance data file.

If you enter the SET EVENT command before entering a SET DATAFILE command, the Collector establishes a default data file. The default data file has the same file name as your program's executable image file and a file type of .PCA.

You can use one event marker per program location. Multiple program locations are enabled for each event name.

Examples

Format

SET FILTER filter-name filter-spec [,filter-spec...]

The SET FILTER Analyzer command creates a new filter definition. When a subsequent PLOT or TABULATE command is entered, the restrictions specified in the filter definition are applied to all data points in the performance data file. A data point passes a filter if it satisfies any one filter restriction in the filter. Only those data points that pass all defined filters are tallied in the histogram or table.

By using multiple restrictions in a single filter, you OR the restrictions; if a data point passes any one restriction, it passes the filter. By using multiple filters, you AND restrictions; a data point must pass all defined filters to be tallied in a histogram or table.

Filter restrictions that do not apply to a given data point are ignored. A file-name restriction, for example, is ignored for page fault data because no file name is collected for a page fault data point.

To use the /MAIN_IMAGE, /STACK_DEPTH, and /CUMULATIVE qualifiers, you must first gather stack PC values using the Collector SET STACK_PCS command.

If you specify /MAIN_IMAGE=prog-unit, /STACK_DEPTH= n, and /CUMULATIVE= n, they are applied in the following order:/MAIN_IMAGE, /STACK_DEPTH, then /CUMULATIVE. Therefore, if you specify the /MAIN_IMAGE=prog-unit and /STACK_DEPTH= n qualifiers, the Analyzer will search for the first stack PC value within the specified program unit. It will not use the data point in this address. However, the Analyzer uses the data point in the address n call frames on the stack from the main image address when it checks address filter restrictions. If you include /CUMULATIVE on that command, the same action occurs, but the Analyzer also uses the PC values in all the call frames below that (or in the first n call frames down, if /CUMULATIVE= n).

Examples

Format

SET IO_SERVICES

The SET IO_SERVICES Collector command enables the collection of I/O system services data. After you enter the GO command with I/O data collection enabled, the Collector intercepts every I/O system-service call during program execution. For each such call, the Collector gathers the appropriate information from the File Access Block (FAB), Record Access Block (RAB), or other parameters, and records it in the performance data file. The exact information gathered depends on the I/O service, but includes the program address of the call, the name of the service, and the CPU time stamp. It might also include the name of the file accessed, the record size of the transfer, the physical I/O read and write counts, and other information.

Example

PCAC> SET IO_SERVICES/STACK_PCS

This command enables the collection of I/O services data and specifies that stack PC values be collected.

Format

SET KEY

When you define keypad keys using the DEFINE/KEY command, you can assign a specific state name to each key definition. The Collector-defined state names are DEFAULT, GOLD, and BLUE. If the assigned state is not set when you press the key, the command string to which the key is bound is not processed. You use the SET KEY command to change the current state so keys for the specified state are processed.

If you do not use the SET KEY command, the current keypad state is DEFAULT.

Example

PCAC> SET KEY/STATE=BLUE

The SET KEY command sets the current state to BLUE. After entering this command, when you press a keypad key with a BLUE definition, that definition is executed (even if you do not press PF4 first). PF4 is the Collector-defined BLUE key.

Format

SET LANGUAGE language-name

The language setting determines how PCA parses symbol names in command input. If the language is set to C or C++, PCA treats symbol names as case sensitive. If the language is set to anything other than C or C++, symbol names are assumed to be case insensitive.

When you use the SET DATAFILE command, the language setting is determined by the language of the main routine in the program. Typically, you need not change this setting. However, if you have a mixed-language program that includes C modules, you must change the language setting with the SET LANGUAGE command before you can reference symbols that include lowercase letters.

Format

SET LOG [file-spec]

The SET LOG command records all PCA input and output in the specified log file. Input is recorded as entered. Output is recorded with a leading exclamation point ( ! ). Because the exclamation point is the PCA comment character, you can rerun the logged PCA session by using the log file as a command procedure.

Example

PCAC> SET LOG [PING]PONG

This command establishes the file [PING]PONG.LOG as the Collector log file. All subsequent commands and their output are recorded in this file.

Format

SET MAX_SOURCE_FILES n

Opening a source file requires the use of an I/O channel, which is a limited system resource. Using the SET MAX_SOURCE_FILES command, you can specify how many I/O channels PCA can use to read source files. If PCA reaches this limit, it must close one source file before it can open and read another one. In such cases, source display still works, but at some performance cost.

By default, PCA keeps up to ten source files open at any one time. Typically, there is no need to change this value.

Example

PCAA> SET MAX_SOURCE_FILES 20

This command sets the number of source files PCA can keep open at one time to 20.

Format

SET MODE keyword [,keyword]

The SET MODE command sets or cancels screen mode and various submodes within screen mode. Keypad mode is enabled by default. You must disable keypad mode only if your program requires the use of the numeric keypad for its own purposes.

Example

PCAA> SET MODE SCREEN, LOG_SCREEN

This command enables both screen mode and the logging of screen images in the log file. Screen images are logged only if output logging in general is enabled with the SET LOG command.

Format

SET NOTE "quoted-string"

The SET NOTE Collector command enables you to describe the current collection run in a quoted string following standard PCA rules for quoted strings. This description is stored in the data file. You can retrieve the note by entering the SHOW RUN_DESCRIPTION command in the Analyzer, or the SHOWNOTE command in the Collector.

Example

PCAC> SET NOTE "G-FLAT"

This command describes the current collection run and stores the quoted string in the data file.

Format

SET PAGE_FAULTS

In addition, the Collector can place its own ASTs in elevated mode, thereby supporting the collection of data from user AST routines.

Example

PCAC> SET PAGE_FAULTS

This command enables the collection of page fault data.

Format

SET PC_SAMPLING

The SET PC_SAMPLING Collector command enables the collection of program counter sampling data. After you enter the GO command with program counter sampling enabled, the Collector samples the program counter (PC) every 10 milliseconds and records each observed program counter value in the performance data file. You can change the sampling interval with the /INTERVAL: n qualifier.

Example

PCAC> SET PC_SAMPLING/STACK_PCS

This command enables the collection of program counter sampling data, and specifies that stack PC values are collected for this measurement.

Format

SET PLOT [nodespec [,nodespec...]]

See the PLOT command for a full listing of applicable qualifiers and their meanings.

The SET PLOT Analyzer command sets the default qualifiers and node specifications used by the PLOT and TABULATE commands. Qualifiers explicitly specified on the PLOT or TABULATE command override the current defaults.

Example

PCAA> SET PLOT/SOURCE/DESCENDING/NOZEROS

After this SET PLOT command is entered, all subsequent PLOT and TABULATE commands use the /SOURCE, /DESCENDING, and /NOZEROS qualifiers unless these qualifiers are explicitly overridden.

Format

SET PROMPT string

Example

PCAC> SET PROMPT MYNAME> MYNAME>

This command changes the Collector prompt from PCAC> to MYNAME>.

Format

SET RUN_NAME run-name

The SET RUN_NAME Collector command establishes a name for the current collection run. When you enter the GO command, this name is recorded in the performance data file. If you do not enter a SET RUN_NAME command, the null run name (the name with zero characters) is recorded. You can use the collection run name to filter performance or coverage data in the Analyzer.

Examples

PCAC> SET RUN_NAME PC_SAMPLE_RUN

This command specifies that the collection run name is PC_SAMPLE_RUN. This run name is recorded in the performance data file when you enter the GO command.

Format

SET SEARCH [parameter,...]

The SET SEARCH command enables you to set the SEARCH command's default qualifiers. If you provide either two parameters or qualifiers that are mutually exclusive (such as the ALL and NEXT parameters), the latter parameter or qualifier in the sequence takes precedence. If you provide a qualifier and a parameter that are mutually exclusive (such as the /ALL qualifier and the NEXT parameter), the parameter takes precedence. Each of the qualifiers can be expressed as a parameter.

Example

PCAC> SET SEARCH IDENTIFIER
PCAC> SHOW SEARCH
      Default search qualifiers:  /NEXT  /Identifier

This command sets the default SEARCH qualifier as /IDENTIFIER.

Format

SET SERVICES

The SET SERVICES Collector command enables the collection of system-services data. When you enter a GO command with system-services data collection enabled, the Collector intercepts every system-service call in the user program and records it in the performance data file. For each call, the Collector records the name of the system service, the program location where it was called, and a CPU time stamp.

Example

PCAC> SET SERVICES/NOSTACK_PCS

This command specifies the collection of system-services data and disables the collection of stack PC values.

Format

SET SOURCE dirname [,dirname...]

The SET SOURCE command directs PCA to a specified list of directories for source files when source text must be displayed. By default, PCA expects a source file to be in the same directory and in the same exact file it was in when it was compiled. If that file has been moved to another location, you must use the SET SOURCE command to specify that location. You must also establish a directory search list with the SET SOURCE command if you want to view source files in a source window when in screen mode. For more information on viewing source files in display windows, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Examples

Format

SET STACK_PCS

The SET STACK_PCS Collector command enables the collection stack PC values for sampling data, CPU sampling data, system-services data, I/O services data, exact execution count data, and test coverage data. The stack PC values for a data point consist of the program counter value and all call stack return addresses for that data point. In addition, you can use the /STACK_PCS qualifier to collect stack PC values for these datakinds, or use the /NOSTACK_PCS qualifier when you do not want to collect stack PC values.

If you collect stack PC values in the Collector, the Analyzer is able to charge back the resources consumed in shareable images (such as the run-time library) to the code in your program that calls the shareable images. To use the stack PC information, use the /MAIN_IMAGE, /CUMULATIVE, or /STACK_DEPTH qualifier with the PLOT or TABULATE command in the Analyzer.

Example

PCAC> SET STACK_PCS

This command enables the collection of stack PC values.

Format

SET TASKING

The SET TASKING Collector command instructs the Collector to gather tasking information. The Analyzer can then associate the gathered data with the task that caused that data to be gathered. Any datakind can be plotted against the TASK domain. This enables you to plot the amount of time or other resource used in various tasks.

To get the Analyzer to report on data by task, specify the SET TASKING command in the Collector, then specify the appropriate domain in the Analyzer by providing that domain's node specification on a PLOT or TABULATE command. For more information on this command and information on creating histograms and tables for Ada-specific domains, see the VSI DECset Performance and Coverage Analyzer for OpenVMS Command-Line Interface Guide.

Example

PCAC> SET TASKING

This command causes tasking data to be collected on all tasks defined in the data file.

Format

SET TERMINAL

The SET TERMINAL command sets the terminal width or page size that PCA uses to format output. It does not reset the terminal itself; you must do that manually. If you are in screen mode, the screen is refreshed.

The default terminal width and page size are determined by your device type, or by the last SET TERMINAL command you entered at DCL level.

Example

PCAA> SET TERMINAL/WIDTH:132

This command specifies that the terminal width is 132 columns.

Format

SET TITLE "title-text" [,"title-text"...]

The SET TITLE Analyzer command establishes up to six lines of title text to be displayed on each page of output from PLOT and TABULATE commands. The new title does not take effect until you enter another PLOT or TABULATE command (it does not affect the current plot or table). Each title line is centered within the current terminal width. After centering, the rightmost 10 columns of the first title line are overlaid with the page number. To prevent truncation, the first title line should be limited to the current terminal width, minus 20 characters of text.

If you have established a multiline title, you can change individual lines within that title by using the /LINE= n qualifier. If/LINE= n is not used, the new title completely replaces the previous title.

If you do not enter a SET TITLE command, “VSI Performance and Coverage Analyzer” is shown on the first title line.

Examples

Format

SET UNALIGNED

On OpenVMS Alpha systems only, the SET UNALIGNED Collector command enables the collection of unaligned, access-fault data. After you enter the GO command with unaligned, access-fault data collection enabled, the Collector records in the performance data file all unaligned, access-fault data that occurs during program execution. The Collector records the alignment-faulting program counter value, the alignment-faulting virtual address, and other information.

Example

PCAC> SET UNALIGNED/STACK_PCS

This command enables the collection of unaligned data and specifies the collection of stack PC values.

Format

SET VCOUNTERS [nodespec [,nodespec...]]

The SET VCOUNTERS Collector command enables the counting of vector processor instructions. The collected data can help you determine to what extent the vector processor is being used. You must specify at least one node specification on the command line to indicate the domain of the data to be collected.

Examples

Format

SET VCPU_SAMPLING

The SET VCPU_SAMPLING Collector command enables the collection of PC values for random vector instructions. The collected data lets you determine the scalar and vector parallelism throughout your entire program.

When you collect vector CPU samples, the sampling interval timer includes only the time that the program is actually running the processor. This form of sampling enables you to focus on the particular areas of the program's algorithm where time is being spent, and not on the areas where outside influences consume time.

Example

PCAC> SET VCPU_SAMPLING/INTERVAL:20/NOSTACK_PCS

This command causes the interval to be 20 milliseconds, and disables STACK_PCS collection for this measurement. For all subsequent SET VCPU_SAMPLING requests, a default of /NOSTACK_PCS will be assumed.

Format

SET VERIFY

The SET VERIFY command causes PCA to echo subsequent command input to the terminal. Input verification is useful when you want to see the commands from command procedures as they are executed. You can disable input verification with the CANCEL VERIFY command.

Example

PCAC> SET VERIFY
PCAC> @X.COM
@X.COM
SET DATAFILE [SAGER.TST]PCAPRIME
SET LANGUAGE C
PCAC>

The SET VERIFY command enables input verification. The next command entered (@X.COM) is echoed to the terminal. Then a SET DATAFILE and a SET LANGUAGE command are read from the command procedure X.COM. Both commands are echoed to the terminal.

Format

SET VPC_SAMPLING

The SET VPC_SAMPLING Collector command enables the collection of PC values for random vector instructions and causes the sampling rate to be applied to the wall clock. The collected data lets you determine the scalar and vector parallelism throughout your entire program.

When you collect vector PC samples, the sampling interval timer includes all idle time associated with the current run of the program. This form of sampling shows you where the time is being spent in the program, with little cost to the time of actually running the program. You can set the time interval by using the /INTERVAL qualifier.

Example

PCAC> SET VPC_SAMPLING/INTERVAL:20/NOSTACK_PCS

This command causes the interval to be 20 milliseconds, and disables STACK_PCS collection for this measurement. For all subsequent SET VPC_SAMPLING requests, a default of /NOSTACK_PCS will be assumed.

Format

SET WINDOW window-name AT

(start-line,line-count,start-column,column-count)

The SET WINDOW command enables you to assign a name to a screen window. A screen window is a region on the screen through which you can view a display. You must specify the window in terms of a starting line number on the screen and a line count. Once defined, you can use a window name in subsequent DISPLAY and SET DISPLAY commands.

PCA provides a substantial number of predefined window names. You can list all the defined window names using the SHOW WINDOW command.

Example

PCAA> SET WINDOW TINY AT (1,2)
PCAA> DISPLAY OUT AT TINY

The first command defines a window named TINY. The top border line for the window is at line 1 of the screen. The window can display two additional lines of text. The second command displays the OUT screen display through window TINY.

Format

SHOW keyword [parameters]

SHOW is not an individual command. Each SHOW command consists of SHOW followed by a required keyword. For details, see the individual SHOW command descriptions.

Format

SHOW ALL

The SHOW ALL command displays all data collection options, definitions, and mode settings you have established. It also displays the name of the log file, the name of the performance data file, and information on all major mode settings. Entering SHOW ALL is the same as entering a number of more detailed SHOW commands.

Example

PCAC> SHOW ALL
Language: FORTRAN
Performance Data File: DEV:[STAR]FFT.PCA;2
Gathering CPU sampling data with STACK_PCS
    AST Timer Interval is 10 ms.
Gathering page fault data
 Default search qualifiers:   /NEXT /STRING

This command displays the name of the log file, the current language setting, the name of the performance data file, and all data collection options.

Format

SHOW ANC

Format

SHOW COUNTERS

Example

PCAC> SHOW COUNTERS
Counters
  Set Counters PROGRAM_ADDRESS BY ROUTINE
  Set Counters LINE PRIMES
\OPENIN\%LINE 22

The SHOW COUNTERS command shows that exact execution counts are collected for every routine in the user program and for line 22 of routine OPENIN in module PRIMES.

Format

SHOW COVERAGE

Example

PCAC> SHOW COVERAGE
Coverages
  Set Coverage  /Until=1  /Previous  PROGRAM_ADDRESS BY CODEPATH

This SHOW COVERAGE command shows that test coverage is measured for every code path in the user program. Each coverage breakpoint is removed the first time it is executed.

Format

SHOW CPU_SAMPLING

Example

PCAC> SHOW CPU_SAMPLING
Gathering CPU sampling data with STACK_PCS, AST Timer Interval is 10 ms.

The SHOW CPU_SAMPLING command shows that CPU sampling data is collected with stack PCs, the sampling interval is 10 milliseconds, and the AST timer interval is 10 milliseconds.

Format

SHOW DATAFILE

Example

PCAC> SHOW DATAFILE/FULL
Performance Data File: DEV$:[PCA.TST]CUMU_MAIN_IO.PCA;1
  Created by: PCA V4.6                 Last updated by: PCA V4.6
  Created on:25-MAR-1998 15:51:19.07   Last updated on:25-MAR-1998-
                   15:51:30.62
 
 Image file: DEV$:[SAGER.TST]PCAPRIME.EXE;19
  Image name: PCAPRIME                         Image  ID: 01
  Image linked on:  8-MAR-1998 13:57:53.14     by Linker: 04-00
 
  There is 1 collection run
  The DST is 481 bytes long
  Known shareable images:
    FORRTL          LIBRTL          PCA$COLLECTOR   DBGSSISHR
    PCA$PRVSHR      LBRSHR          SMGSHR

The /FULL qualifier gives more complete information about the data file.

Format

SHOW DISPLAY

Example

PCAA> SHOW DISPLAY
display SRC at Q123, size = 64, removed, dynamic, kind = SOURCE
display PLOT at Q123, size = 64, dynamic, kind = PLOT
display OUT at E7, size = 100, dynamic, kind = OUTPUT
display PROMPT at E8, size = 64, dynamic, kind = PROGRAM

This command displays the definitions of the default screen displays SRC, PLOT, OUT, and PROMPT.

Format

SHOW EDITOR

Example

PCAA> SHOW EDITOR
The editor is CALLABLE_TPU having the command line:
      "TPU"

This command displays the setting of the editor and its command line.

Format

SHOW EVENT

Example

PCAC> SHOW EVENT
Events
  Set Event COMPUTE LINE PRIMES
\OPENIN\%LINE 22

This command shows that an event marker for event COMPUTE is recorded in the performance data file each time line 22 in routine OPENIN is executed.

Format

SHOW FILTER

The SHOW FILTER Analyzer command lists the name and filter restrictions for each defined filter. Filters determine which data points from the performance data file are tallied by the PLOT and TABULATE commands. You can create filters with the SET FILTER command and delete them with the CANCEL FILTER command.

Example

PCAA> SHOW FILTER
Filter definitions:
  Filter F1:
    RUN_NAME = 1:3
    RUN_NAME = 8
  Filter F2:
    TIME = OUTPUT (event marker)

The SHOW FILTER command shows that two filters are defined. Filter F1 has two run-name restrictions and filter F2 has an event marker restriction.

Format

SHOW IO_SERVICES

Example

PCAC> SHOW IO_SERVICES
Gathering I/O service data with STACK_PCS

The SHOW IO_SERVICES command shows that I/O services data is collected.

Format

The SHOW KEY command displays predefined key definitions, or those keypad definitions established with the DEFINE/KEY command. You can use the /DIRECTORY qualifier to list the names of all states (DEFAULT, GOLD, BLUE, EXPAND, MOVE, and CONTRACT) in which there are key definitions.

Example

PCAC> SHOW KEY KP2
DEFAULT keypad definitions:
  KP2 = "SHOW ALL/FULL"

This command displays the DEFAULT definition for KP2.

Format

SHOW LANGUAGE

Example

PCAC> SHOW LANGUAGE
Language: FORTRAN

This command shows that FORTRAN is the current language.

Format

SHOW LOG

Example

PCAC> SHOW LOG
Output logging on file: USRD$:[USER]PCAC.LOG;1

This command shows that output logging is enabled and gives the name of the log file.

Format

SHOW MAX_SOURCE_FILES

Example

PCAA> SHOW MAX_SOURCE_FILES Max_source_files: 10

This command shows that PCA can keep up to ten I/O channels open for source files at one time.

Format

SHOW MODE

Example

PCAC> SHOW MODE
Mode: noscreen, keypad, scroll, nomovie, nolog_screen

This command shows that keypad mode is enabled.

Format

SHOW NOTE

The SHOW NOTE Collector command enables you to retrieve the currently defined note in the Collector session.

Example

PCAC> SHOW NOTE

This command displays the currently defined note stored in the data file of the Collector session.

Format

SHOW PAGE_FAULTS

Example

PCAC> SHOW PAGE_FAULTS
Gathering page fault data

The SHOW PAGE_FAULTS command shows that page fault data is collected.

Format

SHOW PC_SAMPLING

Example

PCAC> SHOW PC_SAMPLING

The SHOW PC_SAMPLING command shows that program counter sampling data is collected with stack PC values, the sampling interval is 10 milliseconds, and the AST timer interval is 10 milliseconds.

Format

SHOW PLOT

The SHOW PLOT Analyzer command shows both the SET PLOT and the current active plot defaults.

Example

PCAA> SHOW PLOT
Plot and tabulate defaults:
  Qualifiers:
    /PC_SAMPLING /DESCENDING /NOMINIMUM /NOMAXIMUM
    /NOCUMULATIVE /SOURCE /ZEROS /NOSCALE /NOCREATOR_PC
    /NOPATHNAME /NOCHAIN_NAME /WRAP /NOPARENT_TASK /NOKEEP /NOTREE
    /FILL=("*","O","x","@",":","#","/","+")
    /NOSTACK_DEPTH /NOMAIN_IMAGE
  Node specifications:
    PROGRAM_ADDRESS BY ROUTINE
Setting for current plot:
  Qualifiers:
    /PC_SAMPLING /DESCENDING /NOMINIMUM /NOMAXIMUM
    /NOCUMULATIVE /SOURCE /ZEROS /NOSCALE /NOCREATOR_PC
    /NOPATHNAME /NOCHAIN_NAME /WRAP /NOPARENT_TASK /NOKEEP /NOTREE
    /FILL=("*","O","x","@",":","#","/","+")
    /NOSTACK_DEPTH /NOMAIN_IMAGE
  Node specifications:
    TIME BY EVENT

The SHOW PLOT command displays the SET PLOT defaults first. The qualifiers and node specifications of the currently active plot are shown next.

Format

SHOW RUN_DESCRIPTION parameter

Examples

Format

SHOW RUN_NAME

Example

PCAC> SHOW RUN_NAME
Current run name = "STEVE"

This command shows that the name of the current collection run is STEVE.

Format

SHOW SEARCH

Example

PCAC> SET SEARCH ALL, STRING
PCAC> SHOW SEARCH
         Default search qualifiers:  /ALL/STRING

This command shows the current default SEARCH command qualifiers.

Format

SHOW SELECT

EXAMPLE

PCAA> SHOW SELECT
screen mode not set
display selections:
    scroll = PLOT
    input  = none
    output = OUT
    error = PROMPT
    source = SRC
    program = PROMPT
    prompt = PROMPT
    plot = PLOT

The SHOW SELECT command shows that the screen display OUT is the current output display, the display PLOT is the current scrolling display, and so on.

Format

SHOW SERVICES

EXAMPLE

PCAC> SHOW SERVICES
Gathering system service data with STACK_PCS

The SHOW SERVICES command shows that system services data is collected.

Format

The SHOW SOURCE command displays the current, source-directory search lists. The current, source-directory search list determines what directories are searched for source files when source text must be displayed. The source-directory search list is established using the SET SOURCE command.

Example

PCAC> SHOW SOURCE
source directory search list for PCAPRIME:
        [MY_DIR]
source directory list for all other modules:
        []
        SRC$

This command shows that two source-directory search lists are defined: one for module PCAPRIME and one for all other modules.

Format

SHOW STACK_PCS

Example

PCAC> SHOW STACK_PCS
Not gathering stack PC data

This command shows that stack PC values are not collected.

Format

The SHOW SYMBOL command displays symbols in the program address domain, or symbols you have defined with the DEFINE/COMMAND command.

You can use the /ADDRESS and /DIRECT qualifiers or the IN clause only if /DEFINED is not specified. If you do not specify an IN clause, the whole program will be the scope for symbol selection.

The /DEFINED qualifier cannot be used in combination with any other qualifiers to the SHOW SYMBOL command.

Examples

Format

SHOW TASKING

Format

SHOW TERMINAL

Example

PCAA> SHOW TERMINAL
Terminal page size: 24, Terminal width: 80

This command shows that the Analyzer currently assumes a terminal page size of 24 lines and a terminal width of 80 columns when formatting output.

Format

SHOW TITLE

Example

PCAA> SHOW TITLE
Current title text:
  "Welcome to Wonderland"
  "Enjoy your visit"

This command displays the text of the current two-line title.

Format

SHOW UNALIGNED

Example

PCAC> SHOW UNALIGNED
Gathering unaligned access data with stack PCs.

This example shows that gathering of unaligned, access-fault data is enabled.

Format

SHOW VCOUNTERS

Example

PCAC> SHOW VCOUNTERS
  Set Vector Counters MODULE PRIMES BY VINSTRUCTION

The SHOW VCOUNTERS command shows that vector instruction counts are collected for MODULE in the user program PRIMES.

Format

SHOW VCPU_SAMPLING

Example

PCAC> SHOW VCPU_SAMPLING
Gathering Vector CPU sampling data with STACK_PCS, AST time interval is 10 ms.

This command shows that vector CPU sampling data is collected with stack PCs, the sampling interval is 10 milliseconds, and the AST time interval is 10 milliseconds.

Format

SHOW VERIFY

Example

PCAC> SHOW VERIFY
Not verifying commands

The SHOW VERIFY command shows that command input verification is disabled.

Format

SHOW VPC_SAMPLING

Example

PCAC> SHOW VPC_SAMPLING
Gathering Vector PC sampling data with STACK_PCS, AST Timer Interval is 10 ms.

This command shows that vector PC sampling data is collected with stack PCs, the sampling interval is 10 milliseconds, and the AST Timer Interval is 10 milliseconds.

Format

Format

The SPAWN command acts the same as the DCL command SPAWN. You can use it to break out of the PCA session to edit files, read mail, or do any other tasks you would normally do at DCL level, all without ending your PCA session.

Examples

Format

TABULATE [nodespec [,nodespec...]]

See the PLOT command for a full listing of applicable qualifiers and their meanings.

The TABULATE Analyzer command displays the same information as the PLOT command, but in the form of tables instead of histograms. See the PLOT command and the Guide to VSI DECset Performance and Coverage Analyzer for OpenVMS Systems for a full description of the PLOT and TABULATE commands and their qualifiers.

Examples

Format

TYPE [modname[ \line-number[:line-number]]][,...]

The TYPE command enables you to view a line or range of lines in your source code. To use the TYPE command, you might have to establish a source directory search list with the SET SOURCE command.

The modname without any line numbers displays the first line. If you provide only one line number, the corresponding line of source code is displayed. The default line number is the number for the line following the last line displayed. To display the next line, enter the TYPE command without a line number and press the Return key. By repeating this sequence, you can read through your source program one line at a time. For more information on the TYPE command, see the Guide to VSI DECset Performance and Coverage Analyzer for OpenVMS Systems.

Example

PCAC> TYPE COBOLTEST\160,22:24
module COBOLTEST
   160: START-IT-PARA.
module COBOLTEST
   22: 02      SC2V2   PIC S99V99    COMP VALUE  22.33.
   23: 02      SC2V2N  PIC S99V99    COMP VALUE -22.33.
   24: 02      CPP2    PIC PP99      COMP VALUE  0.0012.

This command displays lines 160 and lines 22 through 24 in the module COBOLTEST.

Format

UNDEFINE/COMMAND symbol-name [, symbol-name...]

The UNDEFINE/COMMAND command deletes the specified command symbols. The UNDEFINE/COMMAND command and DELETE/COMMAND command perform the same function.

Example

PCAC> UNDEFINE/COMMAND FOO, FEE

This command cancels the symbols FOO and FEE.

Format

The UNDEFINE/KEY command deletes key definitions established with the DEFINE/KEY command. The UNDEFINE/KEY command and DELETE/KEY command perform the same function.

Example

PCAC> UNDEFINE/KEY KP7

This command cancels the key definitions for KP7.