× 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,
I did not see if someone mentioned this yet but you could use a
rough search using the search tool. When the results are in you can
select those entries returned (collapsing to just the member name),
right click and choose to search over with more specific requirements.
It's the same search as the filter search (it would be nice to turn the
searches into filters sometimes).

The part I dislike about searching is the need to sometimes perform a
negative search (ex. source without the standard elements like an H-SPEC
copy book) AND this second search orders the result member list.

Thanks, Matt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Kurt Anderson
Sent: Tuesday, March 02, 2010 12:35 PM
To: 'Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries'
Subject: Re: [WDSCI-L] WDSCi shop moving to IBM i 6.1

Vern,

Thank you for the mentioning the menu option for the flashlight... (not
sure why you used ellipses).

Sorry, I figured since we were discussing searching over source files on
the iSeries I didn't need to mention which tab on the Search window I
was using. You are correct, however, it is indeed the iSeries Search
tab.

There is definitely a difference between Find String over a filter and
the blanket search function. For instance, I just ran a search over a
source file with 15 source members (the filter is really just a
representation of the source file in its entirety). It took over a
minute to run. Using the Search function with the same search criteria
over the same file took about 5 seconds.

I can understand the difference, I'm not questioning that (or anything
really), I'm just pointing out the different options and the search
speeds involved.

Thanks,
Kurt Anderson

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Vern Hamberg
Sent: Tuesday, March 02, 2010 11:39 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries
Subject: Re: [WDSCI-L] WDSCi shop moving to IBM i 6.1

The flashlight button is the same as going to the Search menu of the
menu bar and clicking Search...

In the window you see when clicking the flashlight, you should be using
the iSeries search tab. That uses the FNDSTRPDM command behind the
covers.

Which kind of search do you use from the flashlight button? There are
over half a dozen different ones.

"Find string" executed as you describe is also the same search mechanism

under the covers - it just limits you to the filter or whatever. I know
it is the same, because the search text is the same as I entered in a
prior search using the iSeries search option of the Search menu.

HTH
Vern

Kurt Anderson wrote:
Hi Michael,

I'm on WDSC 7.0 as well and this is what I've found out about
searches.

Search via the flashlight icon just below the menu will allow very
fast searching an entire source member (and even multiple sources so
long as they have similar names). This is the "Search" function.

Performing a "Find String" is much slower, and if done over a source
file with many members may take a while to run. This is accessible via
right-clicking a source member or filter and getting the pop-up menu.
(It may be accessible in other ways, however I only know of the ways I
mentioned.)

Hope that helps,

Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Koester, Michael
Sent: Tuesday, March 02, 2010 9:11 AM
To: WDSCI-L@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] WDSCi shop moving to IBM i 6.1

Thanks for that, Dave. The one feature I still fall back to PDM for
is
string-search through our source members. I've not found anything
acceptable in WDSC here - it just dies trying. I suspect that has
been
resolved in RDi/RDP? If indeed that is no longer an issue, I could do
w/o ADTS.



Prior to my original post, I reviewed the discussion on the archives
from last August (Subject: Re: [WDSCI-L] justifying RDi when WDSCi
'still works'), and wondered if the sentiments have changed, or if new
justifications for upgrade have become obvious.



-- Michael

~~~~~~~~~~~~~~~~~~~~~~~~



WDSCi 7.0 runs against 6.1 just as well as it runs against V5R4. I
haven't used any of the 6.1 compiler enhancements, so I'm not quite
sure
what to expect there. I know it won't prompt them, just not sure what
the verifiers and syntax checkers will make of them.



I don't know how your ADTS entitlements compare to your actual
requirements, but that's also something your management needs to look
at. Maybe if you have extra ADTS licenses, you can reduce your RDP
costs through the upgrade option, if that's available to you. I tried
to work that angle, but it didn't pan out here.



Dave Shaw

Mohawk Industries





----- Original Message -----

From: "Koester, Michael" <mkoester@xxxxxxxxxxxxx>

To: <WDSCI-L@xxxxxxxxxxxx>

Sent: Tuesday, March 02, 2010 8:32 AM

Subject: [WDSCI-L] WDSCi shop moving to IBM i 6.1






Word from system admin is that we will soon be on i 6.1. I am using



WDSC V 7.0.0.8 (7.0.0.20090225_1508) and I have concerns that our
WDSC



development environment may soon need to go RDi/RDP. I understand

that


WDSC does not "grow" with post-v5r4 advances to RPG.





First question: How successful is running WDSC in the IBM i 6.1



environment?






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.