Why does Datacom Dataquery show different SELFR and SELNR statistics for equivalent DQL mode FIND versus SQL mode SELECT requests?
For example, the following DQL query:
FIND ALL PERSONNEL
PRINT NUMBER, NAME, CITY-ADDRESS, STATE-ADDRESS, SOCIAL-SECURITY
Resulting statistics:
Current Dataquery FIND/SELECT Statistics.
------------------------------------------------------------------------
DATAQUERY: FIND STATISTICS QUERY NAME:
------------------------------------------------------------------------
NUMBER REQUESTED: ALL COMPLETION DATE: 12/30
NUMBER FOUND: 200 COMPLETION TIME: 12:24
FIND TERMINATED BECAUSE: NORMAL END OF SEARCH WAS REACHED
OVERALL OPTIMIZATION SEARCH
------- ------------ ------
ELAPSED TIME (SECONDS): 0 0 0
I/O EVENTS: 16 0 16
SELFR TOTAL: 2 1 1
SELNR TOTAL: 201 201
TOTAL BYTES: 264
While the following SQL query retrieves the same records but shows zero (0) SELFR and SELNR in the statistics:
SELECT NUMBER, NAME, CITY_ADDRESS, STATE_ADDRESS, SOCIAL_SECURITY FROM SYSUSR.PERSONNEL
Resulting statistics:
Current Dataquery FIND/SELECT Statistics.
--------------------------------------------------------------------------DQEF0
DATAQUERY: FIND STATISTICS QUERY NAME:
-------------------------------------------------------------------------------
NUMBER REQUESTED: ALL COMPLETION DATE: 12/30/2016
NUMBER FOUND: 200 COMPLETION TIME: 12:24:51
FIND TERMINATED BECAUSE: NORMAL END OF SEARCH WAS REACHED
OVERALL OPTIMIZATION SEARCH
------- ------------ ------
ELAPSED TIME (SECONDS): 0 0 0
I/O EVENTS: 0 0 0
SELFR TOTAL: 0 0 0
SELNR TOTAL: 0 0
TOTAL BYTES: 0
The statistics shown state that those are from the "FIND". TheDatacom Dataquery statistics SELFR and SELNR statistics are only available to Dataquery for DQL mode.
This is working currently as designed since for Dataquery in SQL mode, all the processing is in done within the Datacom Multi-User (MUF) space.
In order to get those statistics, you would need to set up and tailor Datacom Accounting to capture the specifics from the MUF.