I use QCLSCAN all the time for just this purpose, with no noted
performance impact.  One advantage over SCAN is it's easier to match
lower and upper case search arguments and data.  One technique SYNON
used years ago is to count the number of records scanned and report back
to the user if that for example, 500 records were processed, here are
the results, and there are more records to be checked if they so desire.

Alan Novick
Pressman Toy Corporation
New Brunswick, NJ

Denis Robitaille wrote:
> I have an application that display in a subfile a list of all products
> ordered by product number. It shows the product number and the product
> description. The user can request to see only the products that have a
> certain caracter string in their description (Ex: all products with the
> word "ROLLS" in them somewhere). To do that, they type the string to
> look for and the program read the file by product number and, for each,
> scan the description for the string. The string can be anywhere in the
> product description. Currently, i use the SCAN opcode to do the
> scanning. It works great in the test environnement but in production
> (with a lot more products), it is way to slow. I do load the subfile a
> page at a time. I think the delay is due to the SCAN opcode and i am
> thinking of replacing it with the QCLSCAN API. But before going any
> further, i tought i'd ask around. What do you think is the fastest way
> to do this?
> Any help would be apriciated
> --
> Denis Robitaille
> Cascades Inc.

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "".
| To unsubscribe from this list send email to
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].