Re: RdI vs SEU

There may be communication issues when it comes to the speed of WDSCi\RDi\RDP.

Our programmers develop in test environment. The test environment is a relatively small partition of an IBM i located several hundred miles away in another state. Between the size of the partition and the speed of the Internet connection, we commonly experience short delays.

The green screens handle the delays well. They freeze for 1-2 seconds (sometimes several seconds) and then continue processing like nothing happened.

WDSCi\RDi can't handle these delays. They hang for 30-90 seconds (or more) and then give us pop-up messages telling us about communication delays. I haven't tested RDP. But I'm guessing it's the same. RDP likely communicates with the IBM i the same way as RDi.

We talked with IBM and their response was: WDSCi\RDi\RDP working as designed, move your box to where your developers are located or upgrade your hardware (system partition and Internet technologies).

WDSCi\RDi\RDP are more sensitive to communication delays with the IBM i than the ADTS tools.

Kelly

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Monday, March 15, 2010 10:37 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RdI vs SEU

David Gibbs wrote:

On 3/15/2010 7:05 PM, Joe Pluta wrote:

Sadly, I can't agree entirely with that ... RDi / RDp have a long way to go when it comes to CL. That's primarily what I use SEU for now.

What's your biggest complaint? The auto-correct, or the line length?

Speed ... WDSC, RDi, & RDp, all take a huge amount of time parsing large, pre-formatted, CL lines. The editor will hang up for 30-45 seconds on each edit of a statement.

Seriously?? When you say "large" what do you mean? Hundreds of
characters? Thousands? Big, complex expressions? I've had delays
measured in seconds, but never more than perhaps 10.

Joe