× 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.



Kurt,

On your filters you can hold down ctrl and select the filters or filter
results you wish to search, then right click on one of them and it will
search all selected. I do that alot - I think its in here, or here or...

Jim

On Fri, Aug 28, 2009 at 4:04 PM, Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx
wrote:

Jim,

I have all the filters set up that I need... never realized there was that
Find String option. I suppose I should give myself more "discover" time
with WDSC. Thanks for pointing that out.

Ok, I see what you mean about wildcard with the library. That's good,
however it requires a similarity in library names for it to work. Like, it
works for my test libraries because they all start with KJA*. However, it
doesn't work when I'm looking at production source because they are named
different (UPOLIB, FIVLIB, etc.). What had me thinking I couldn't search
multiple libraries is when I was trying to type them out (delimited by a
semi-colon) and was stopped after the 10th position.

-Kurt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jim Essinger
Sent: Friday, August 28, 2009 4:53 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] justifying RDi when WDSCi 'still works'

Kurt,

I am on WDSC 7.0. I use search in two different ways.

a) I create a filter that shows multiple source files. For example if I
know I'm looking in RPG or CL files, I will create a filter that shows me
all the CL or RPG source files from all the source libraries (ours end in
*SRC). Once I have those shown, I can right click on the filter name, and
choose "Find String" from the popup menu.

b) If I am looking for source members with a specific naming pattern, I
will
create a filter for that, then I can search that filter.

I think there is another way to get the search started, If you use the
Search drop down menu, you can find a search string on iSeries by naming
the
connection, library (and you can use wild cards for library, file and
member
name like *src) file, member and what type of file gets searched. You can
also specify column if you like. I had not done this before, so I tried to
find all occurances of a file name in all my source library that had *CL*
in
the source file name. It finished in just a few seconds, and displayed the
results.

Note that I have filter pools turned on, so I can have multiple filters set
up for multiple connections.

HTH

Jim



On Fri, Aug 28, 2009 at 3:16 PM, Kurt Anderson <
kurt.anderson@xxxxxxxxxxxxxx
wrote:

I can't seem to search multiple libraries in WDSC 7.0. Anyone know if
that
was new with RDi?


--
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.
--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.