PCAA> PLOT PROGRAM BY MODULE

      Program counter sampling data is plotted by default. The
      vertical axis has one histogram bar for each module in
      the program. It also has one bar for each shareable image
      used. Each bar indicates how much time is consumed in the
      corresponding program unit.

  PCAA> PLOT/PAGE_FAULTS/SOURCE MODULE FOO BY LINE

      The histogram has one bar for each line in module FOO of the
      user program. The length of each histogram bar is proportional
      to the number of page faults that occurred at the corresponding
      line. Because the /SOURCE qualifier is present, the text of
      each source line is shown next to the histogram bar for that
      line.

  PCAA> PLOT/NONCOVERAGE/SOURCE MODULE FOO BY CODEPATH

      The histogram has one bucket for each codepath in module FOO.
      Any codepath that is not covered has a full-length histogram
      bar. Thus, the histogram highlights code that is not tested.
      The text of each source line is shown next to the corresponding
      codepaths.

  PCAA> PLOT/IO_SERVICES/MAIN_IMAGE PROGRAM BY ROUTINE

      The number of I/O system service calls is plotted along the
      horizontal axis. The routines of the program are plotted along
      the vertical axis. I/O data originating in shareable images
      (such as the Run-Time Library) are charged back to the routines
      in the main image (the user program) that called the shareable
      images to cause I/O.

  PCAA> PLOT/SERVICES/DESCENDING/NOZEROS SYSTEM_SERVICES BY SERVICE

      The names of the OpenVMS system services are plotted along the
      vertical axis. The number of calls on each system service is
      plotted along the horizontal axis. The histogram is sorted so
      that the most frequently used services are listed first. All
      system services that were never called are omitted from the
      histogram.

  PCAA> PLOT/PHYSICAL_IO_COUNTS FILE_NAME BY FILE

      The names of the RMS files opened or created by the program are
      plotted along the vertical axis of the histogram. The number
      of physical I/O operations for each file is plotted along the
      horizontal axis.

  PCAA> PLOT/VCOUNTERS INSTRUCTION BY VOPCODE

      This command causes the report view to be based on the
      disassembled opcode for each vector instruction in the
      entire application that is sampled. The number of times a
      vector instruction is used lets you see if your application
      is spending a lot of time performing certain operations.
      For example, if you see that the SYNC vector instruction
      is executed more than any other vector instruction, you can
      infer that the scalar processor is spending too much idle time
      waiting for the vector processor to finish an operation.