Find String Function -- 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: [WDSCI-L] Find String Function
From: Duane Kehoe <dkehoe@xxxxxxxxxxxxxx>
Date: Tue, 29 Mar 2005 10:28:46 -0600
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for 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/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

   I need a little help with the find string function(particularly it's
   options / settings).  I am trying to find a field's usage across an entire
   file(many source members <~1500) and I am finding that WDCS is submitting
   ~1500 individual find strings thus creating ~1500 spool files.  I need to
   know if there is any way to change this behavior via preferences, I have
   looked through but can not see anything.  What I would really like to do
   is have it run across the entire library and then generate a single
   listing, without creating my own command in RSE that is.  Any help here is
   greatly appreciated.
   --

   Weyco Group -             
                             
       Florsheim, Brass Boot, Nunn Bush, Stacy Adams
   Duane Kehoe                       Phone # 414.908.1814 
   EC / Programmer / Analyst           Fax # 414.908.1610 
                             Email: dkehoe@xxxxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

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.