Re: Scanning text in source files in RDi -- WDSCI-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Scanning text in source files in RDi
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Thu, 29 Jun 2017 13:52:48 -0400
List-archive: <http://archive.midrange.com/wdsci-l/>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

On 6/29/2017 1:30 PM, John Yeung wrote:

And to take this a step further: If (for whatever reason) you can't
get RDi to search quickly enough, you can always fall back on
FNDSTRPDM executed directly on the server. At least for simple cases
like this, where you're searching for a literal string (and not some
regex, for example).

AFAIK, RDi uses FNDSTRPDM under the covers.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Scanning text in source files in RDi , John Yeung
Re: Scanning text in source files in RDi , Vernon Hamberg

This mailing list archive is Copyright 1997-2024 by midrange.com 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.