Analyzer Command

    Processes performance or coverage data and displays the processed
    data in tabular form. The TABULATE command accepts the same
    qualifiers and parameters as the PLOT command, and it displays
    the same information as the PLOT command, but in the form of
    tables instead of histograms.

    Format

      TABULATE  [nodespec [,nodespec...]]

1  –  Parameters

 nodespec

    Specifies a program location. Node specifications specify how the
    table should be partitioned into buckets. See HELP Nodespecs for
    information about node specifications.

2  –  Description

    See PLOT for a full discussion of the PLOT and TABULATE commands
    and their qualifiers.

3  –  Examples

  PCAA> TABULATE PROGRAM BY ROUTINE

      This command tabulates program counter sampling data by default
      since no data-kind qualifier is specified. The resulting table
      has one entry for each routine in the program. Each entry
      shows the number of program counter values collected from the
      corresponding routine, what percentage this is of the total
      number of PC values collected, and how wide the 95% confidence
      interval is.

  PCAA> TABULATE/COUNTERS/SOURCE MODULE FOO BY LINE

      This command tabulates exact execution counts for each line
      in module FOO. (This assumes that such execution counts were
      collected in the data file.) The /SOURCE qualifier causes the
      text of each source line to be shown next to the table entry.

  PCAA> TABULATE/PAGE_FAULTS TIME BY 100 MSECS

      This command generates a table showing the number of page
      faults in each 100-millisecond time interval since the start
      of the collection run. The intervals represent CPU time.
      Inspection of this table may reveal page faulting peaks at
      various times during program execution. Such peaks often occur
      when a program switches from one phase of execution to another;
      the new phase typically requires a different set of code and
      data pages from those in the previous phase.

  PCAA> TABULATE/IO_SERVICES FILE_KEY BY KEY

      This command creates a table showing the number of RMS calls
      that performed I/O using no key, a primary key, a secondary
      key, or a higher-order key. Keys are used to access indexed
      sequential files. Primary key access is more efficient than
      secondary key access. Thus, if more I/O is done on secondary
      keys than primary keys, I/O may go faster if the key positions
      are switched.