

System Output › Overview Of Program Reports › Program Summary Report › Program Summary Report Fields
Program Summary Report Fields
Here is an explanation of the fields that make up the Program Summary Report. See Figure 2-9.
REPORT TITLE--The title line contains the name of the report, the name of the application program (or CA IDMS/DC task) being reported, and whether that program executed as an ONLINE or BATCH run-unit.
INTERVAL--This line lists the start and stop date/time of the time interval being reported. The data displayed here depends on what you selected using the START, STOP, and INTERVAL parameters and on the actual date/time of the program activity being reported.
RUN UNITS TOTAL--Total number of run-units terminated within the reported time interval.
COUNTS--The following 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 from the database.
- 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 the program performed during the time interval.
TOTAL CPU (100THS SEC)--Total CPU time needed to execute the program during the time interval specified reported in units of 1/100 seconds.
MEAN VALUE--Average value per run-unit occurrence within the reported time interval.
ACCUMULATED VALUE--Total value for all run-unit occurrences within the reported time interval.
% OF SYSTEM OCCURRENCES--This ratio (expressed as a percentage) is the accumulated value for this run-unit against the accumulated value for all selected run-units active within the reported time interval. This highlights the run-units that are consuming the largest amount of system resources.
RATIOS--A list of five ratios follows.
- 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 field shows ratios of less than one (1).
Copyright © 2014 CA.
All rights reserved.
 
|
|