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



The only complaint I have about the WDSC Iseries Search vs. PDM (and it
is a minor one) is that the wildcard specifications for the member seem
more limited.

For instance, given our source file naming conventions, I can search for
all finance applications by putting "FN*" in the member search criteria
field, or I can search for all CL programs by entering "*C". But I
can't search for all Finance CL's by entering "FN*C", whereas I can do
that in PDM.

But I definitely like seeing all my results in the window at one time
with their context. Much better than having to look through all of them
one at a time like FNDSTRPDM.

G

|-----Original Message-----
|From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]
|On Behalf Of Joe Pluta
|Sent: Friday, June 27, 2008 10:23 AM
|To: Websphere Development Studio Client for iSeries
|Subject: Re: [WDSCI-L] Painfully slow searching
|
|Tim Gornall wrote:
|> In Remote Systems view, when I do a find string on a member filter,
it
|is
|> painfully slow. It took minutes for 98 members.
|Searching a filters is slower than searching files, because searching a
|filter does it one member at a time.
|
|> In PDM, it takes seconds for hundreds of members.
|A client/server function is going to be slower than one which is
|entirely on the host. Always. With search, you have to perform the
|entire search, then download the results to the workstation. There's
no
|real way to speed it up other than searching the entire file which
|reduces the interactions between the client and the server.
|
|> And I can auto open them for edit, etc.
|You can open them one at a time, in the order they appear in the file,
|without context, and then use F16 to search through each file to see
the
|other occurrences. I never liked that, although it's the best you can
|get with PDM.
|
|With the RDi search, you see all the occurrences in every member, in
|context, and can double-click on the ones you want to open the file to
|that source line. It's a somewhat different concept.
|
|You can also search across multiple libraries and files, but it's not
at
|5250 speed.
|
|> Am I missing something, there must be a better way...
|>
|If what you're interested in is getting to the first member in a file
|that has a match on a string, or printing a list of matches in a file,
|then PDM is faster because it's entirely on the host. If you are
|interested in reviewing all the matches in a set of members and then
|opening the members based on context, then RDi is a better tool.
|
|Joe
|--
|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 ...

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.