SQL debug gobbledygook

Hi to all,


I have an RPG pgm that searches a client file using surname, forename and date of birth.

If I enter surname='F', forename =' ' and date of birth='26.11.1988' (am I really THAT old), the program takes a long time to show the results.

It does a SETGT on a logical with the keys surname, forename, date of birth and client number set to 0, followed by reads until surname isn't like 'F'.


I wanted to check the file in an SQL session. I typed

SELECT CCLTNM, CCLTPR, CNADL FROM mylogical WHERE surname>'F' ORDER
BY surname, forename, dateOfBirth

to see all the records my RPG program had to read.

This request also takes a long time to execute. In debug mode, I see "Reason Codes for supplementary access paths have been used". Message CPI432A emmitted, something about timing out of the optimizer. Maybe because of Select in the DDS of the logical and the non compatability with SQE? This is why I specified the logical on my SQL statement.

Then I see "Access path created for mylogical file".
This is because of code reason 1 :Exécution des critères de classement/groupage indiqués. Which I think means I've specified the sorting.

The access path created is on surname,forename, dateOfBirth. Which is the same as the file in the request.
Why is it creating this access path?


Would someone enlighten me?