For a DQL Language query, <PF6> STATS displays the Find Statistics panel as shown in the following sample. The panel provides statistical information on the execution of your query or dialog.
Find Statistics (DQEF0)
=> Current Dataquery FIND/SELECT Statistics. ------------------------------------------------------------------------DQEF0 DATAQUERY: FIND STATISTICS QUERY NAME: ----------------------------------------------------------------------------- NUMBER REQUESTED: ALL COMPLETION DATE: 01/06/2000 NUMBER FOUND: 9 COMPLETION TIME: 15:37:40 FIND TERMINATED BECAUSE: NORMAL END OF SEARCH WAS REACHED OVERALL OPTIMIZATION SEARCH ------- ------------ ------ ELAPSED TIME (SECONDS): 1 0 0 I/O EVENTS: 0 0 0 SELFR TOTAL: 0 0 0 SELNR TOTAL: 0 0 TOTAL BYTES: 0 ----------------------------------------------------------------------------- <PF1> HELP <PF2> RETURN
Panel Description
A brief explanation of the fields on the Find Statistics panel follows:
Name of the query to which these statistics apply.
Number of rows requested in your query.
Number of rows found or counted in the database.
Date that the search for this query ended.
Time that the search for this query ended.
Error Messages
You may receive the following messages:
The FIND process completed normally.
The FIND exceeded the value set for the I/O limit in the System Option Table parameter SRCHLIM=. Either reduce the number of rows which CA Dataquery is to FIND, or request that your CA Dataquery Administrator increase the value in the SRCHLIM= System Option Table parameter so that your query can finish the FIND processing.
The FNDBLKS= parameter for the user is too small. Consider increasing the value specified for this user on the User Table Maintenance panel. See Adding a New User for more information.
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 request that the CA Dataquery Administrator increase the maximum time allowed in the MFTIME= System Option Table parameter.
This query has been canceled from the requesting user's terminal.
This query was canceled from another terminal.
ELAPSED TIME (SECONDS)
The overall time elapsed in seconds to process the FIND statement.
The process of determining the FIND strategy for searching the database efficiently.
The actual search time against the database for the FIND statement.
I/O EVENTS
The overall number of CA Datacom/DB physical I/O events for the processing of the FIND statement.
The number of CA Datacom/DB physical I/O events used for determining the database search strategy.
The number of CA Datacom/DB physical I/O events used for the search of the database by the FIND statement.
SELFR TOTAL
The overall number of CA Datacom/DB Compound Boolean Selection SELFR (select first) commands that were issued to execute the FIND statement.
The number of CA Datacom/DB Compound Boolean Selection SELFR (select first) commands that were issued for determining the database search strategy.
The number of CA Datacom/DB Compound Boolean Selection SELFR (select first) commands that were issued for the search of the database by the FIND statement.
SELNR TOTAL
The overall number of CA Datacom/DB Compound Boolean Selection SELNR (select next) commands that were issued to execute the FIND statement.
(Nothing is printed under OPTIMIZATION.)
The number of CA Datacom/DB Compound Boolean Selection SELNR (select next) commands that were issued for the search of the database by the FIND statement.
TOTAL BYTES
The overall number of bytes that were required to hold the internal control blocks that CA Dataquery built to process the FIND statement.
(Nothing is printed under OPTIMIZATION.)
(Nothing is printed under SEARCH.)
Extended Statistics
The following statistics appear on this panel if the STALL command has been used:
The number of times tables were joined during query processing.
The number of joins that could be used. Valid joins never exceed total joins. The more tables there are involved, the smaller the percentage of joins that are valid. CA Dataquery considers every possible join and chooses the optimum combination.
An estimate from the lowest cost join.
An estimate from the lowest cost join.
|
Copyright © 2014 CA.
All rights reserved.
|
|