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



I for one do you not use CODE. I find it to be faster to use RLU and
SDA than to use CODE.

Sharon Wintermute


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Justin Taylor
Sent: Wednesday, March 03, 2010 8:02 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] WDSCi shop moving to IBM i 6.1

Wouldn't a more accurate comparison be WDSc & CODE vs. RDP? If someone
is already using WDSc, what are the chances they're still using RLU &
SDA?

Just a thought...




date: Tue, 02 Mar 2010 16:52:21 -0600
from: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] WDSCi shop moving to IBM i 6.1

Koester, Michael wrote:
Follow-on question: Under i/OS 6.1, at what point does it become
significantly advantageous to buy/configure/learn RDP?

Immediately. Maybe sooner. :)

Seriously, I've got an article coming out in tomorrow's MC Press that
addresses just that fact. The Screen Designer and Report Designer in
RDP should be enough to make you move. These features are no longer a
"technology preview" (which simply meant that Brian Farn hadn't had
enough time to finish it), and they're light years ahead of SDA (we
won't even sully them with a comparison to the Really Lousy Utility
<grin>). If you do any 5250 development, then RDP is going to make you
more productive. Period.

And this is for V5R3 and V5R4 folks as well. RDP will back-connect just

fine.

Joe

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.