Re: Is RDi ready for prime time? (was: iSociety Fireside Chat recording available)?

I would concur with most of Joe's opinions. I'm fully sold on WDSc and
I'm certain I will be on RDi. However, there are functions which fall in
my responsibility as a senior analyst which I can't do in the workbench (a
generic term to make this simple). For example, at times I produce lists
of objects or source members with WRKOBJPDM. I use these as a checklist
for a project--e.g., upgrades of purchased applications, changes in
business rules, etc. WDSc (and I'm assuming RDi) don't print lists from
the table view, the RSE-tree view, iSeries search view, etc. Until such
time, I'll *need* an ADTS license to do my job--I can't do my job without
it. But I emphatically don't want to do my development in SEU.

I think there's no argument that editing is better in the workbench, but
the workbench hasn't replaced all the functions of PDM--particularly the
WRKxxxPDM functions. (Just to be clear, I like some of the features of
the table view or a filter better--e.g., member lists crossing multiple
source files, etc.)

Just my 2-cents worth

wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/07/2008 09:11:09 PM:

date: Thu, 07 Feb 2008 16:50:11 -0600
from: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] iSociety Fireside Chat recording available?

Jon Paris wrote:

On 7-Feb-08, at 3:43 PM, Joe Pluta wrote:

The only way this wouldn't work is if they said that the entitlement
seats couldn't upgrade, and that would be simply a double-tax on
existing users and I'd expect the entire community to go up in arms.

The other problem Joe, as you know, is that RDi does not support all
of the functions of ADTS and until such time as it does it is not
practical for most users to switch even they want to.

I honestly don't see the point in lobbying for such a switch if the
replacement tool can't do the job. It makes more sense to me to
lobby IBM for a low-cost upgrade - say $200 - which would let you use
both.

Are you saying that you don't recommend RDi and CODE over SEU and SDA?
That's odd; I thought you have been advocating CODE for a long time, and

RDi is of course light years ahead of SEU. I'm relatively certain that
RDi will include CODE Designer, or did you hear otherwise?

In fact, I can't find any reason not to move to RDi (with CODE as a
stopgap until Screen Designer gets finished) with the possible exception

of the performance issue on large source files that Dave Shaw has been
experiencing.

Into the opinion piece, where I'll just express mine since opinions are
like... well, everyone has one. I think letting people use both is the
problem we have today. I think people should migrate from SEU to RDi,
saying goodbye to the old tool, with one copy left on the machine for
emergency use. I suppose allowing both is also an option, but I worry
that it would be an excuse for some of the recalcitrant to not move.
SAeems pretty much a coin flip; I prefer the outrate trade-in, but
that's just me.

Joe