RE: Reasons for %Lookup failure

 >> Yup.  That fixed it.  I guess I understand the purpose of the ASCEND
keyword, or at least when not to use it.  Thanks!

So that others don't get the wrong impression Tony, I would like to point
out that in your example you _should_ have used ASCEND.

As Paul mentioned, you should have used the fourth parameter on %Lookup to
inform the BIF that the array was not fully loaded and therefore to
constrain the number of entries searched.  This would have cured your
problem and given you better performance than removing the Ascend keyword.
%Lookup is far better/faster than the old LOOKUP op-code but with the
constraint that you must mean what you say <grin>.  You coded that the whole
array was in ascending sequence - it wasn't.  It had a bunch of blank
entries at the end that were out of sequence and caused your original
problem.

For anyone who is interested in the "nuts and bolts" of this issue check out
the article "Look before you %lookup" which we wrote for the eXtra
newsletter.  You can find it at
http://www.eservercomputing.com/iseries/articles/index.asp?item=DIRECT&sid=1
0&id=498 or via our web site at http://partner400.com/ArticlesEXTRA1.htm

Jon Paris
Partner400
www.Partner400.com