A description of the fields common to SREPORTs 005 through 009 follows:
Specifies the time period specified on the USE 'SREPORT 000' parameter where SELECTED FROM specifies the beginning date and time and SELECTED TO specifies the ending date and time. The date is in Julian form, yyddd, where yy is the last two digits of the year and ddd is the day. The time is in hh:mm form, where hh is hours based on a 24-hour clock and mm is minutes.
Specifies the actual time period for the report generated. If the USE 'SREPORT 000' parameter does not specify a time range, CV SYSTEM START/INTERVAL START and TO represent the time range for the entire input archive file or input file created by SREPORT 099. When the input file contains cumulative statistics, the CV SYSTEM START date and time will be displayed. When the input file contains interval based statistics, the INTERVAL START date and time will be displayed.
Specifies the starting job name of Central Version which collected the statistics.
Specifies the number of Central Version which collected the statistics.
Indicates the total number of tasks executed within the actual time frame of the report. This label appears on SREPORTs 005, 006, 007, 008, and 009.
Indicates the total number of transactions executed within the actual time frame of the report. This label appears on SREPORTs 010, 011, and 021.
Indicates the number of programs called.
Indicates the number of programs loaded from disk (either a load area or a load/core-image library).
Indicates the number of terminal reads performed.
Indicates the number of terminal writes performed.
Indicates the number of terminal I/O errors.
Indicates the number of requests to acquire storage dynamically from storage pool.
Indicates the number of requests to retrieve scratch records from the DDLDCSCR area.
Indicates the number of requests to place scratch records in the DDLDCSCR area.
Indicates the number of requests to delete scratch records from the DDLDCSCR area.
Indicates the number of requests to get queue records from the DDLDCRUN area.
Indicates the number of requests to store or replace queue records in the DDLDCRUN area.
Indicates the number of requests to delete queue records from the DDLDCRUN area.
Indicates the number of requests for the date and time of day.
Indicates the number of requests to define an event that is to occur after a specified time interval.
Indicates the number of times requests for database services (for example, OBTAIN record-name) were issued by the task.
For LRF and SQL programs, this value should be less than or equal to the number of CALLS TO DBMS. You can use these values to evaluate how efficiently the LRF or SQL path extracts data. For example, a program OBTAIN logical-record command increments NUMBER DB SERVICE RQSTS by one, but may greatly increment the CALLS TO DBMS value, especially if an area sweep occurs due to the NULL SELECT clause.
Indicates the number of database pages read from disk.
Indicates the amount of CPU time (in ten-thousandths seconds) spent executing user code. DC/UCF collects user-mode time statistics if enabled in the STATISTICS TASK clause of the SYSTEM system generation statement.
Indicates the amount of CPU time (in ten-thousandths seconds) spent performing DC/UCF services for the task. DC/UCF collects system-mode time statistics if enabled in the STATISTICS TASK clause of the SYSTEM system generation statement.
Indicates the amount of time spent on I/O requests and waiting for other system resources. The value is the difference between wall-clock and CPU time for the task.
Indicates the number of database pages physically written to disk for the transaction. A page can be updated several times before it is actually written back to the database.
Indicates the number of database pages requested by IDMSDBMS (including pages found in a buffer). A page request does not result in a page read if the page is in the buffer pool.
Interpretation: The ratio of NUMBER PAGES REQUESTED to NUMBER PAGES READ is the buffer utilization ratio. The buffer utilization ratio measures the effectiveness of the buffer-pool size and design of the database (for example, CALC and VIA clustering). The higher the ratio the better. Ratios consistently below 2.0 indicate that processing is random or that the buffer-pool size is too small.
The buffer utilization ratio may be artificially high for transactions that keep locks, due to the nature of the internal locking mechanism. IDMSDBMS cannot hold a buffer while requesting a lock; therefore, when locks are kept, IDMSDBMS must free and request a page each time a record is requested.
Indicates the number of CALC records stored on the target page.
Indicates the number of CALC records not stored on the target page.
Interpretation: The ratio of NO OVERFLOW records to the total number of CALC records stored is the CALC cluster ratio. Ideally, the ratio should be 1, which indicates no overflow. Ratios less than 1 or less than the norm indicate space utilization is getting high and the database should be tuned.
Indicates the number of VIA and/or DIRECT records stored on the target page.
Indicates the number of VIA and or DIRECT records not stored on the target page.
Interpretation: The ratio of NO OVERFLOW records to the total number of VIA records stored is the VIA cluster ratio. Ideally, the ratio should be 1, which indicates no overflow. A value less than 1 or less than the norm indicates very large data clusters, high utilization of space, or small page size.
Indicates the number of records requested by the DBMS.
Interpretation: The ratio of NUMBER RECORDS REQUESTED to NUMBER PAGES REQUESTED is the space management ratio. The space management ratio measures how well space is allocated (for example, VIA options, CALC distribution, and buffering). The higher the ratio the better. Ratios less than 4 or less than the norm indicate the size of the buffer should be increased and database tuning should be performed.
The space management ratio may be artificially high for transactions that keep locks, due to the nature of the internal locking mechanism. IDMSDBMS cannot hold a buffer while requesting a lock; therefore, when locks are kept, IDMSDBMS must free and request a page each time a record is requested.
Indicates the number of records made current of the transaction.
Interpretation: The ratio of NUMBER RECORDS REQUESTED to NUMBER RECORDS CURRENT OR RU is the effectiveness ratio. The effectiveness ratio measures how much work the CA IDMS/DB has to do to find the requested record. The lower the ratio the better. If the ratio is high, examine set options (for example, sorted order or next pointers only) for appropriateness. If the options are correct, examine the program logic for accurate use of currency.
Indicates the number of noncontiguous segments stored for variable-length records.
Indicates the number of records relocated from the home page.
Indicates the number of calls to the database management system.
Note: Execution of each navigational DML request involves one call; execution of each logical record facility (LRF) or SQL request typically involves multiple calls.
Indicates the number of SR8 splits.
Indicates the number of SR8 spawns.
Indicates count of Index members or SR8s whose up-level pointers were corrected to point to the actual SR8 in which they appear.
Indicates number of Btree index probes.
Indicates the number of SQL commands executed.
Indicates number of tuples FETCHed.
Indicates the number of rows INSERTed.
Indicates the number of rows UPDATed.
Indicates the number of rows DELETEd.
Indicates the number of all locks acquired and released by all completed transactions. This is NOT a count of locks currently held.
Indicates count of SR8s created.
Indicates count of SR8s erased.
Indicates count of SR7s created.
Indicates count of SR7s erased.
Indicates the number of SQL sorts performed.
Indicates the number of rows participating in all sorts.
Indicates the number of automatic access module recompilations.
Indicates the amount of CPU time (in microseconds) spent in executing system code.
Indicates the amount of CPU time (in microseconds) spent in executing user code.
Indicates the amount of CPU time (in microseconds) spent on zIIP.
Indicates the amount of CPU time (in microseconds) spent on CP, while qualified for zIIP.
Indicates the amount of CPU time (in microseconds) spent on CP in either system mode or user mode.
Indicates the amount of CPU time (in microseconds) spent on CP or zIIP, while qualified for zIIP.
|
Copyright © 2013 CA.
All rights reserved.
|
|