ENQUIRY search time is very different from EB.READLIST ()

Hi,
Query FBNK.STMT.ENTRY through simple ENQUIRY, the query conditions are ACCOUNT.NUMBER and VALUE.DATE
Time spent 3 seconds, there are 6 results

But use 'LIST FBNK.STMT.ENTRY WITH ACCOUNT.NUMBER EQ "XXX" AND VALUE.DATE EQ "YYYYMMDD"'
Time spent 2 minutes, the result is also 6

Or use SSELECT to call CALL EB.READLIST () in the subroutine, which also takes longer

Why is there such a big difference?

The total number of FBNK.STMT.ENTRY is 900,000
R13 on windows

Thanks

Hi
what was executed first?

ENQUIRY uses SELECT (as well as EB.READLIST does) and after the first run the data is cached. You need to test all again in a new session each try.

Hi VK ,

Thank you very much for the reply.

After restarting the browser, the enquiry query still takes 2-3 seconds.
But the repeated use of SELECT query still takes 2 minutes,
the same result in PROGRAM and BUILD.ROUTINE and CONVERSION.ROUTINE.

Hi
in Browser case things are cached not there but in jAgent session - restart jbase_agent to be sure.

Still I don't believe that 900,000 records are processed in 3 seconds. Does this enquiry use a concat file?

Last but not least - why would you run select in conversion routine?

Hi ,

SELECT in CONVERSION.ROUTINE is just to test the time of SELECT.
At first, I doubted whether it was related to the system variables of ENQUIRY.
ENQUIRY does not use concat file, just a simple ENQUIRY.
I tried to change the ACCOUNT.NUMBER and VALUE.DATE of the query in ENQUIRY, but every few seconds can be found.

Conversion routine is triggered as many times as there are records in ENQ output...

to do a clean test run enquiry from terminal and compare it to jQL SELECT.