Re: Embedded SQL performance question.

> when I run it in the RPG program the optimizer builds its own access 
path
> and takes 3 minutes to execute. 
> 

I think it depends on when the logical was created. I think the optimizer 
search for logical up to a certain point. If it is not in that range it 
creates it's own.   So if say the logical that matched your SQL was the 
third one created over the PF it would find and use but say it was the 
nineteenth it would not. Could be wrong but thought I remembered this 
problem with BPCS a while back. Do not know if optimizer has changed. Do 
know that  I fixed a lot of BPCS long running jobs by recompiling Logicals 
in a order that the SQL's could pick them up. But like I said it has been 
a while and things do change.

Thanks 
Bill Hopkins