After a user has executed a query or a dialog and routed the report to a printer or a terminal, he can produce statistical information on the execution of the query or dialog. The statistics are printed to the printer automatically if he was authorized with STATISTICS specified Y. To display the statistics, he can use a PF key or issue the STATISTICS command. The statistics are reset with each query execution.
The terminal display of the statistics is as follows:
=> CURRENT DATAQUERY FIND/SELECT STATISTICS. ------------------------------------------------------------------------DQEB0 DATAQUERY: FIND STATISTICS QUERY NAME: ----------------------------------------------------------------------------- NUMBER REQUESTED: COMPLETION DATE: NUMBER FOUND: COMPLETION TIME: FIND TERMINATED BECAUSE: OVERALL OPTIMIZATION SEARCH ------- ------------ ------- ELAPSED TIME (SECONDS): I/O EVENTS: SELFR TOTAL: SELNR TOTAL: TOTAL BYTES: ----------------------------------------------------------------------------- <PF1> HELP <PF2> RETURN
The following is a brief explanation of the fields on the Find Statistics panel.
Name of the query to which these statistics apply.
Number of rows requested in your query.
Number of rows found in the database.
Date that the search for this query ended.
Time that the search for this query ended.
|
Field |
Reason |
Explanation |
|---|---|---|
|
FIND TERMINATED BECAUSE:
|
NORMAL END OF SEARCH WAS REACHED |
The FIND process completed normally.
|
|
SITE I/O LIMIT (DQOPTLST.SRCHLIM) EXCEEDED |
The FIND exceeded the value set for the I/O limit in the System Option Table (DQOPTLST) parameter SRCHLIM=. Either reduce the number of rows which CA Dataquery is to FIND, or increase the value in the SRCHLIM= parameter so that your query can finish the FIND processing. |
|
|
MAX WORK TABLE BLOCKS EXCEEDED |
The number of blocks specified in the FNDBLKS= parameter has been exceeded. You must evaluate the limit you have set and determine what is best for your site. If needed, you can override the FNDBLKS= value for this user using the USERS option. |
|
|
MAX ELAPSED TIME EXCEEDED |
The maximum time allowed for the processing of a query FIND has been exceeded. Either simplify the FIND so that the FIND processing time is shorter or increase the maximum time allowed using the System Option Table MFTIME= parameter. |
|
|
FIND CANCELED |
This query has been canceled from the requesting user's terminal. |
|
|
FIND CANCELED |
This query was canceled from another terminal. |
|
Field |
Column |
Description |
|---|---|---|
|
ELAPSED TIME (SECONDS):
|
OVERALL |
The overall time elapsed in seconds to process the FIND statement. |
|
OPTIMIZATION |
The process of determining the FIND strategy for searching the database efficiently. |
|
|
SEARCH |
The actual search time against the database for the FIND statement. |
|
|
I/O EVENTS:
|
OVERALL |
The overall number of CA Datacom/DB physical I/O events for the processing of the FIND statement. (I/Os are calculated on USER databases. No I/Os are calculated to the terminal or DQF or DQW.) |
|
OPTIMIZATION |
The number of CA Datacom/DB physical I/O events used for determining the database search strategy. |
|
|
SEARCH |
The number of CA Datacom/DB physical I/O events used for the search of the database by the FIND statement. |
|
|
SELFR TOTAL:
|
OVERALL |
The overall number of CA Datacom/DB CBS SELFR (select first row) commands that were issued to execute the FIND statement. |
|
OPTIMIZATION |
The number of CA Datacom/DB CBS SELFR (select first row) commands that were issued for determining the database search strategy. |
|
|
SEARCH |
The number of CA Datacom/DB CBS SELFR (select first row) commands that were issued for the search of the database by the FIND statement. |
|
|
SELNR TOTAL:
|
OVERALL |
The overall number of CA Datacom/DB CBS SELNR (select next row) commands that were issued to execute the FIND statement. |
|
OPTIMIZATION |
(Nothing is displayed in this column.) |
|
|
SEARCH |
The number of CA Datacom/DB CBS SELNR (select next row) commands that were issued for the search of the database by the FIND statement. |
|
|
TOTAL BYTES:
|
OVERALL |
The overall number of bytes that were required to hold the internal control blocks that CA Dataquery built to process the FIND statement. |
|
OPTIMIZATION |
(Nothing is displayed in these columns.) |
When the statistics are printed, they are the same as those displayed.
|
Copyright © 2014 CA.
All rights reserved.
|
|