Re: Advised index not used but still advised

David

Nothing is wrong - this is standard SQL stuff. Think "host variable" or "parameter marker" - if you prepare a SELECT in embedded SQL, you put a question mark in the statement in the place where you want a varialbe value. This is called dynamic SQL, as opposed to static SQL. The optimizer by default can handle literals as parameter markers, which lets the statements be treated as a single statement - if it kept the literals, then there would be a distinct statement for each literal value or set of values.

To see what value was used, the best way now is to use Visual Explain. The display of VE will have the access plan in the form of a tree on the left, with all kinds of information in a panel on the right. At the top level, there will be the statement itself, as well as a comma-separated list of the values that replaced each respective parameter marker.

Look at the documentation for PREPARE in the SQL Reference, for starters.

HTH
Vern

David FOXWELL wrote:

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Charles Wilt

If you know which job was servicing the request, and know
that the request was just issued, there's a "Show Last SQL"
statement option you can use from iNav.

Hey that's great to know, Charles. I just tried it and got this :

select *from mytable where myfield = ? In a 5250 SQL session I'd typed select *from mytable where myfield = ' '

Is the question mark normal or do I need a fix? If the request was inbedded in an RPG with a host variable, should I be able to see the last value for that variable?