Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
IMS CPU timing in MainView for IMS
The MainView for IMS Offline Performance Reporter and Transaction Accountant components report various CPU timing figures for IMS. The timing figures are accumulated by the Event Collector and then maintained in IRUF transaction and program records.
Offline reports show several categories of IMS CPU time. The categories help you analyze CPU time usage patterns. Here are some examples of CPU measurement categories:
- Overhead / Chargeable
- CPU time that results from system processing
- CPU time that results directly from a user action
- Application / DL/I / DB2 / Overhead
- CPU time that the application program accumulates
- CPU time that IMS DL/I processing accumulates
- CPU time that DB2 request processing accumulates
- CPU time that other IMS or operating system overhead functions accumulate (such as scheduling, open/close activity, or other system processing)
- Control Region / Message Region
- CPU time that the IMS control region or DLISAS region accumulates
- CPU time that is accumulated in the dependent region (message region or batch message region) in which the application was scheduled
This section contains the following topics:
Related topic