HP 3000 Manuals

HP SPT/XL User's Manual: Analysis Software

Chapter 2  Using HP SPT/XL 

This chapter takes you through the flow diagram in figure 2-1 to give an
overview of how to use HP SPT/XL. You can then continue on to chapter 3
and do these steps for yourself in a hands-on tutorial.


          Figure 2-1.  Using HP SPT/XL 

HP SPT/XL follows a collection-and-analysis approach to program tuning.
Collection uses sampling and tracing techniques to gather data.  Analysis
provides online reports for evaluating the data.

   1.  Starting at the HP SPT/XL Main Menu, first you must decide whether
       or not you want to collect performance data on your application
       program.  If you need this information, select the  Collect key to
       display the Collection Menu, then follow the steps necessary for
       starting HP SPT/XL's data collector.  The collected data is stored
       in an HP SPT/XL logfile.

       See the HP SPT/XL User's Manual:  Collection Software for details
       on HP SPT/XL's data collection function.

       If you already have performance information in an HP SPT/XL
       logfile, choose the  Analyze key to display the Logfiles screen.
       Enter the name of your HP SPT/XL logfile.

   2.  You may enter the name of either a "raw" or "restructured"
       logfile.  A restructured logfile is one in which you have already
       indicated to HP SPT/XL what you want defined as a transaction.  If
       the logfile you select is already restructured, the Transaction
       List screen is displayed showing the transactions you've
       defined.  From here you can select a function key to display
       transaction-specific performance information online.

       If you enter the name of a raw logfile--one where you have not
       defined transactions for HP SPT/XL, the Logfile Summary
       Information screen will be displayed giving general performance
       information about your entire program.

   3.  On the Logfile Summary Information screen you are prompted for
       whether you want to define transactions.  If you don't define
       transactions, HP SPT/XL views the entire program as a single
       transaction and will be treated as such.

       Defining transactions usually gives you more specific data for
       identifying where you can optimize your program.

       You can choose to define transactions in either of two ways:

       a.  When you first access a new logfile, the Logfile Summary
           Information screen is displayed.  The prompt on the screen
           asks if you want to define transactions.  If you respond YES
           or ENTER, you will be able to define transactions.  If you
           respond NO, HP SPT/XL will treat the entire program as one
           transaction.

       b.  While you are analyzing a logfile, you can select the  
           Redefine Trans function key at any point.

   4.  In defining transactions, HP SPT/XL takes you through a series of
       steps, briefly summarized in figure 2-2.


          Figure 2-2.  Steps in Defining Transactions 

       a.  During the first step in defining transactions, HP SPT/XL
           scans the logfile looking for "events" (or intrinsics) that
           could potentially be used to define the start of a logical
           transaction.  HP SPT/XL recognizes an extensive list of
           intrinsics as possible beginnings of transactions.  (See
           appendix D for a list of intrinsics monitored by HP SPT/XL.)
           You can also modify your program to include STARTTRAN and
           ENDTRAN intrinsics that HP SPT/XL will recognize as delimiters
           of transactions.  (See appendix B for an explanation of the
           STARTTRAN/ENDTRAN intrinsics.)

       b.  The default transactions defined represent HP SPT/XL's best
           guess based on this initial scan.  They are displayed on the
           Transaction Defaults screen.  You then verify that these
           accurately reflect the transactions in your program.

       c.  If the transactions listed on the Transaction Defaults screen
           are not correct, select either  Add to List or  Reject List.
           You can then select the specific intrinsics that define
           transactions in your program by iteratively going through the
           Intrinsic Categories and Transaction Definition screens until
           the transactions are correctly defined.

       d.  Once transactions are defined, the logfile is restructured
           around these transactions and the Transaction List screen is
           displayed.  Now you will be able to review performance data
           that is specific to a transaction.

   5.  At this point you can select an online report for review.  The
       following types of data are available by selecting a function key:

         Summary information

         Intrinsic information

           Frequency of use
           Processing time/CPU time
           Calling location
           Major wait states
           COBOL and PASCAL verbs used with execution times

         File use

           Frequency of access
           Processing time/CPU time used in accessing
           Disk blocks transferred

         TurboIMAGE database use

           Sets accessed and modes of access
           Intrinsics used
           Buffer use statistics
           Lock and hashing conflicts

         Code file sample information

           Program file and library files used

         Individual transactions

           Summary of CPU/processing time
           Intrinsic traces
           Response time histograms

MPE/iX 5.0 Documentation