From: Carsten Flensburg <email@example.com> > A new way of dealing with this potential performance problem was recently > introduced. - V5R1 added the %LOOKUP built-in-function which allows you to > specify a fourth optional parameter specifying the maximum number of > compares to perform. > > If you set this parameter to the current number of elements loaded, you > ensure that no unneccessary compares are performed if the lookup might end > unmatched. > Alternatively you could store the value looked for at the n+1'th position (n is number of occupied positions). Then you always find it; if its position turned out to be n+1, you know that it wasn't there. This will work with any release.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.