Call stack analysis is useful, for example, when data is gathered
    in an RTL. This allows the Analyzer to "charge back" the data
    to the lines within the program that caused the data to be
    gathered. It can also be helpful when you need to know the
    dynamic relationships between portions of your program.

    Call stack analysis requires that call stack data be gathered. To
    gather call stack data, use the Collector SET STACK_PCS command
    or use the /STACK_PCS qualifier with the SET command used to
    gather data.

    The PLOT, TABULATE, INCLUDE, and SET FILTER commands accept the
    following qualifiers:

    /MAIN_IMAGE[=prog-unit]     Start at the top of the stack and use
                                the first PC within the main image or
                                prog-unit if provided.
    /STACK_DEPTH=n              After doing /MAIN_IMAGE, go "n"
                                frames down the stack and use that
                                PC instead.
    /CUMULATIVE[=n]             Charge the rest or "n" PCs to the
                                appropriate buckets.

    The PLOT and TABULATE commands can also produce a dynamic call
    tree. This will show all the call chains in the data being
    plotted and their frequency. The following nodespec will produce
    a dynamic call tree of the specified granularity.

       CALL_TREE BY CHAIN_MODULE
       CALL_TREE BY CHAIN_ROUTINE
       CALL_TREE BY CHAIN_LINE

    The SET FILTER command accepts the following filter
    specification:

       CHAIN_NAME=chain-name