RE: Find String Function

I've used the iSeries search from the menu bar, and it also generates all those 
spooled files. It is still very cool - the library can be generic, such as 
SRC*, and the file cna be generic, such as Q*. But this will take some time for 
it to make the list that comes from these settings (resolving, it says), and 
each entry is a separate FNDSTRPDM - or equivalent? - under the covers. So it 
is still a problem, as far as I'm concerned, that a lot of searches, or a 
generic search, leaves detritus on the system.

Vern

-------------- Original message -------------- 

> Hi Rick, 
> 
> > I'm not familiar with the find string function you are referring to 
> 
> I had the same problem that Duane was describing. When you right-click a 
> filter in the Remote Systems view, you have a "Find String" option. When 
> you use that, it does exactly what Duane was describing, creates a spooled 
> file for each member, searching each one individually... takes forever!! 
> 
> > I use the search option from the menu and select iSeries. It prompts for 
> > a string, library, file (can be all by using *), and member (again, can 
> > be all). 
> 
> I'll have to try that. It never occurred to me that WDSc would have more 
> than one way to search for a string in a member... I had already given up 
> and used FNDSTRPDM (which worked perfectly for what I was doing, and I was 
> able to complete the search, fix the code and deploy it before the WDSc 
> Find String had even completed!) 
> 
> Next time, though... I'll try your suggestion. 
> -- 
> This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing 
> list 
> To post a message email: WDSCI-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l 
> or email: WDSCI-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/wdsci-l.