I can't seem to search multiple libraries in WDSC 7.0. Anyone know if that was new with RDi?
Indeed, the results of the search is beautiful. The source and exact line of code is a double-click away.
The compare source tool is great as well. Although I wish I could type in the source I wanted instead of having to browse for it. (Browsing for source in WDSC/RDi is painfully slow.)
One thing WDSC (and RDi, if I recall correctly from my trial period) is that when you browse you can't see source description. I can't imagine using RDi alone to find source as a new employee at an institution that has programs with numeric names (e.g. MXA00105).
I've tried to maneuver myself to use WDSCi as my PDM tool as much as I can, preparing for the day we go to 6.1 and I foolishly offer my ADTS seat away, although in my eyes it's more of a sacrifice to get the editor I want vs. an improved PDM environment.
-Kurt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Friday, August 28, 2009 3:54 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] justifying RDi when WDSCi 'still works'
Porterfield, Sean wrote:
From: Joe Pluta
Search featuer alone pays for the price of the tool. But that's just me.
What's the search feature you mentioned twice in this thread that's so great? Find within a source member or something else?
Search in RDi is fantastic. You can search a member, a file, or a
library, you can search multiple files across multiple libraries, you
can use wildcards, you can even create your own filters which select
arbitrary members and then scan against that. Think of it as PDM option
on ultra-steroids.
More important to me, though is the fact that it shows you ALL the
matches in a nice, succinct tree view, showing the entire matching line
so that you can easily see which matches makes sense. And then, you
simple double-click on a line and the source is opened and positioned to
that line.
For me, it saves me anywhere between five minutes and a half an hour a
day, sometimes more.
(Note: If I'm editing RPG, I'm going to use WDSCi not SEU. As for ADTS vs RDi licenses, PDM is still extremely useful for many things, and our security officer regularly uses SEU to display/print programs for auditors. She would not be happy to be forced into using a bloated PC package when SEU loads in less than a second.)
I hear this complaint over and over. I don't see it because I always
have it open. I open RDi when I reboot my PC and leave it up, sometimes
for weeks at a time. That being said, I don't consider it a tool for
system operators (or auditors). It's a programmer's tool.
Joe
midrange.com
