Interpreting Fast Path analysis reports

The analysis reports show the origin, database activity, and processing events for each transaction code, although most reported items show average and maximum values.

The reports produced are:
  • Overall summary by transaction

    Summarized by transaction code, the transit times and input/output message lengths are given. The database calls and buffer usage are also included.

  • Exception detail

    For those transactions selected, the terminal origin and routing code are given for each individual occurrence of the transaction. The detail also includes the data appearing in the overall summary.

  • Summary of exception detail by transaction code

    This report is based on the transactions in the exception report. The items reported are the same as for the overall summary.

  • Summary of transactions by PSB

    All programs that are in non-message-driven regions, MPP regions, and BMP regions that enter the sync point processing are reported. The items reported are the same as the summary of exception detail.

  • Recapitulation of the analysis

    This is a documentation aid that gives the grand totals of transactions input to the analysis, and the I/O for online utilities.

The combination of the interval covered by the system log input to the utility and the exception criteria you define in the input control statements determines the content of these reports.

Examples of the reports format and the definition of the items reported can be found in IMS Version 15.2 System Utilities, within the description of the Fast Path Log Analysis utility.

Following are some suggestions for interpreting the reported events:
  • Examine the summary reports and investigate the reasons for sync point failure.
  • Examine the summary report to see if buffer usage was consistently under the NBA values. Check all negative differences that indicate the need for overflow buffers to see that they were unusual occurrences.
  • Compare the database call counts to those of the expected profile. Select those transactions that show unusual patterns for a run to produce a detailed exception report.
  • Examine the balancing group queue counts to see if they are conforming with the scheduling algorithm expectations.