The green screens hang because of temporary bottlenecks in IBM i processing and/or momentary delays in Internet transmissions. This is what I'm told. I'm neither a system administrator or a networking expert.
All I know for sure is that developers see their green screens freeze up for brief moments on a fairly regular basis. If WDSCi\RDi\RDP behaved the same way as the green screens, we would be okay. But they don't. WDSCi\RDi\RDP don't see the message they were expecting from the IBM i, so they hang in some kind of waiting loop for 30-90 seconds, then pop up a message saying they're having communication problems.
This has been a real obstacle in our adopting WDSCi\RDi\RDP. The 30-90 second delays wipe out a lot of productivity and make the tools too frustrating. And the costs of changing the environment to get rid of the delays makes RDi\RDP an even harder sell to managers. Why not avoid those costs and stick with the free ADTS for now, and see what happens down the road?
Kelly
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryce Martin
Sent: Tuesday, March 16, 2010 10:41 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RdI vs SEU
I'm afraid I'd have to agree with IBM on this issue. There is no way a
green screen should *hang* for a second or two because of communications.
But, you guys do what you can afford and tolerate, I just know that I
wouldn't be able to stand it. Our box used to be a couple of hundred
miles away as well and we never had any issues like that. What kind of
connection is set up between your WAN points?
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
Kelly Cookson <KCookson@xxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/16/2010 09:00 AM
Please respond to
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
To
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
cc
Subject
Re: [WDSCI-L] 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
midrange.com
