RDi has a neat tool to create a graphical display of how your subroutines/procedures are interconnected. The tool is still in its infancy, but I have high hopes for it.
The outline running in background is absolutely wonderful. Now if only the verify would as well (or only lock the current source).
I used the RDi 90-day trial while on v5r4. I asked a similar question a while ago (oh, probably at the start of that 90-day trial) and to be quite honest, got the same responses, and none of them really convinced management that it's time to put money down and switch.
Hopefully when we go to 6.1 there'll be more justification (in that RDi supports the 6.1 enhancements while WDSC does not).
I do suggest learning to do as much in WDSC/RDi that you normally would do in PDM. As Kelly stated, giving up your ADTS seat might get you a discount.
What I really miss is searching a compile listing - can't do that in RDi/WDSC (it's like an image or something).
-Kurt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Albert_Slezak@xxxxxxxxxx
Sent: Friday, August 21, 2009 2:36 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] justifying RDi when WDSCi 'still works'
Doesn't RDi have the graphical interface for creating screens and
printfiles and WDSE uses the CODE/400 or was that just hype from IBM I
heard.
Al Slezak
Information Systems Division / NEWS Group
Phone: (630) 451-7433
Fax: (630) 451-7401
Albert_Slezak@xxxxxxxxxx
Making the Magic Happen
Tom Liotta <qsrvbas@xxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
08/21/2009 02:30 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
wdsci-l@xxxxxxxxxxxx
cc
Subject
Re: [WDSCI-L] justifying RDi when WDSCi 'still works'
David Gibbs wrote:
Dave Shaw wrote:
The few of us who use WDSCi here are trying to convince management that
we
should purchase a few licenses for RDi now that we've gone to V6R1. The
pushback we're getting is that WDSCi still works fine, so we need to
justify
spending the money. Has anyone else successfully done this, and if so,
what
approach did you use?
From my perspective, the changes between WDSC 7.0 and RDI 7.5 do not
justify the cost.
People at IBM might argue that RDI 7.5 is a total rewrite of the product
(and I can vouch for that, as I had to do a lot of work to adapt the MKS
Implementer plug-in to work with both versions), but the the functionality
is largely the same.
These comments of David's might touch on a currently intangible
aspect. A rewrite often is needed in order to create a foundation
for future enhancements.
RDI 7.5 will be followed by RDi 7.(5+x) or RDi 8.0, whatever is
coming in the future. Will it be easier to jump from WDSCi to what's
coming in the future? Or will an intermediate RDi 7.x be needed anyway?
Sooner or later, RDi is where it will be. What can be said about
having some of it in place sooner as opposed to doing it all at once
some day?
I've often seen messes when upgrades are delayed until they're forced.
Tom Liotta
midrange.com
