|
|
SOS TurboIMAGE Database MainThe TurboIMAGE Database Main screen (Figure 19.1) provides a comprehensive summary of performance data for databases located on the system. This includes accumulated data for all databases, for each database and for the database that is consuming the greatest amount of resources - the "Hog Database".
Figure 19.1 SOS TurboIMAGE Database Main screenTo access this screen you have to press a shortcut key. This screen is available via shortcut from any other “SOS–TurboIMAGE” screens.To access the TurboIMAGE Database Main screen from any SOS display screen:From the Screen Selection Menu screen or at Enter Screen Code prompt, enter I (Turbo Image Database Main Screen). The TurboIMAGE Database Main screen will display. An example of the screen is shown in Figure 19.1. Theory of Operation
This section provides a brief description of how the ImageStats feature is able to collect and display TurboIMAGE performance information.Collecting Data
Any application that makes use of TurboIMAGE does so by calling TurboIMAGE intrinsics. SOS/ 3000 with ImageStats will, as an option, intercept all such calls for the purpose of taking statistics and reporting them. It does this by using a feature of MPE/iX called Procedure Exits. This feature enables SOS/3000 to execute functions, called handlers, both before and after the execution of each TurboIMAGE intrinsic. In this way the handlers can count the intrinsic calls, keep track of their success or failure, and measure the elapsed time and CPU time consumed.
The information obtained about intrinsic activity is stored by the handlers in an MPE file named ICOLL.PUB.LPS. This file is read and written using mapped file access, so it is very fast.
When SOS/3000 starts up with ImageStats enabled, it makes sure that the ICOLL.PUB.LPS file exists, and that the handlers are "armed" (enabled to be called when the intrinsics are called).
All of the handlers for all of the TurboIMAGE handlers must share access to the ICOLL.PUB.LPS file. A handler locks the file while it is being accessed. If another file tries to lock the file at the same time, it will be unable to do so, and it will not wait. In such a case, data will be lost. The percentage of intrinsic calls for which data was collected is displayed on the TurboImage Database Main screen as the data item ISCol%.
There is a mode wherein 100% of the data will be collected. However, this mode carries a somewhat greater risk to your system if there are program errors. Please contact Lund Performance Solutions for more information regarding this collection mode.Displaying Data
In order to display data, SOS/3000 accesses the data collected by the handlers in ICOLL.PUB.LPS. It performs various computations on the data and then displays it on the ImageStats screens.Stopping Data Collection
The handlers can tell whether the data they are collecting is being used; that is, they can tell whether there is any instance of SOS/3000 running that is using the data in ICOLL.PUB.LPS. If the data is not being used, they will quit collecting it. There will still be handler code that executes when an intrinsic is called, but it will do almost nothing. The handlers can be disabled altogether by running the program TIPEUTIL.PUB.LPS.TurboIMAGE Database Main Screen Keys
Each of the TurboIMAGE Database Main Screen key is listed and explained in the following table.Table 19.1 TurboIMAGE Database Main Screen keysTurboIMAGE Database Main Screen Display Items
TurboIMAGE Database Main
The TurboIMAGE Database Main portion of the screen displays the following information.Table 19.2 SOS TurboIMAGE Database Main data itemsKey Stats for All Databases
The Key Stats for All Databases portion of the screen displays the following information.Table 19.3 SOS Key Stats for All Databases data itemsKey Stats for Hog Database
The Key Stats for Hog Database portion of the TurboIMAGE Database Main screen displays the following information.Table 19.4 SOS Key Stats for Hog Database data itemsActivity Against All Databases by Intrinsic
The Activity Against All Databases by Intrinsic portion of the screen displays the following information.Table 19.5 SOS Activity Against All Databases data itemsThe counters and times for each of these data items are:CPU/I - The average CPU time during the current interval used per DBI call performed by all processes on all databases (measured in milliseconds). Ela/I - The average completion time per DBI call performed by the any processes on all databases during the current interval. Int/s - The average number of calls per second, calculated for DBI calls performed by all processes on any database—a separate count for each item. Activity per Database
The Activity per Database portion of the TurboIMAGE Database Main screen contains performance data for each database accessed by any process on the system. The databases are indexed by their name; however, the user will have to use TIDBID to refer to them.Table 19.6 SOS Activity per Database data items
|
Lund Performance Solutions www.lund.com Voice: (541) 812-7600 Fax: (541) 812-7611 info@lund.com |
|
|