System Output › About CA IDMS Log Analyzer Management Reports › Management Highlights/Program Summary Report › Management Highlights/Program Summary Report Fields

Management Highlights/Program Summary Report Fields

These fields make up the Management Highlights/Program Summary Report. See Figure 2-12.

REPORT TITLE--This line lists the title of the report.

PROGRAM NAME/TYPE/INTERVAL--This line lists the name of the application program whose run-units are selected for reporting, its processing type (whether the run-units are ONLINE or BATCH), and start/stop date and time of report.

RUN UNITS TOTAL--Total number of run-units terminated within the reported time interval.

LOWEST--Lowest value encountered for any run-unit within the reported time interval.

HIGHEST--Highest value encountered for any run-unit within the reported time interval.

MEAN--Average value for all run-units within the reported time interval.

MEDIAN--Median value for all run-units within the reported time interval.

COUNTS--The IDMS STATISTICS (taken from the log record) are reported.

• PAGES READ--Number of pages read from the database.
• PAGES WRITTEN--Number of pages written to the database.
• PAGES REQUESTED--Number of pages requested from the database.
• CALC RCDS ON HOME PAGE--Number of CALC records stored on the home page.
• CALC RCDS OVERFLOW--Number of CALC records stored on an overflow page.
• VIA RCDS ON OWNER PAGE--Number of VIA records stored on the owner page.
• VIA RCDS OVERFLOW--Number of VIA records stored on an overflow page.
• RECORDS REQUESTED--Number of records requested.
• RECORDS BECOMING CURRENT--Number of records made current of run-unit.
• CALLS TO IDMSDBMS--Number of DML verbs executed.
• FRAGMENTS STORED--Number of record fragments stored.
• ROOTS OR RCDS RELOCATED--Number of records relocated because of fragment recomposition.

TOTAL I/O--Total number of database input/output operations performed by the program during the time interval.

TOTAL CPU (100THS SEC)--Total CPU time used by the program during the time interval specified.

RATIOS--The Ratios are reported in four values: Lowest, Highest, Mean, and Median.

• PAGES REQUESTED / PAGES READ--This ratio measures the effectiveness of buffer pool size and allocation. Small ratios (less than 2.00) can indicate random processing, inadequate buffer pool size, or the need for additional buffer pools. A ratio of 20 is generally considered high.
• RECORDS REQUESTED / PAGES READ-- This ratio measures the overall effectiveness of space management, CALC synonym handling, VIA options, and buffer management. Large ratios usually indicate effective buffering (i.e., the minimizing of database I/O). A ratio of 20 is generally considered high.
• RECORDS REQUESTED / RECORDS BECOMING CURRENT--This ratio measures the amount of processing transparency provided by CA IDMS. High ratios (a ratio of 20 is generally considered high) indicate that an excessive amount of database traversing is occurring before target records are retrieved. Pay close attention to sorted sets, sets without PRIOR or OWNER pointers, or program strategy that does not use currency efficiently.
• CALC RCDS OVERFLOW / CALC RCDS ON HOME PAGE--This ratio measures the randomness of the CALC field values, or how full particular database areas are. Large ratios or steadily rising ratio values show that there are either a large number of CALC synonyms, or that space may be getting scarce and that one or more areas may need to be enlarged. Ideally, this field will show ratios of less than one (1).
• VIA RCDS OVERFLOW / VIA RCDS ON OWNER PAGE--This ratio measures the effectiveness of the storage of VIA records, or how full database areas are. Large ratios or steadily increasing ratio values can show that there is a lack of clustering or packing of VIA records (near the associated OWNER record), or a lack of randomness of the OWNER record types of VIA member records. Space may be getting scarce and one or more areas may need to be enlarged. Ideally, this ratio will show values of less than one (1).