Brandon,
I'll not try to put words in Joe's mouth, but I read his point as "On systems where all access is via network port, SEU offers no better access than the client toolsets (WDSC, RDi, Code/400)". With twinax, one could access the system whether the network was up or down. SEU offered a reliable means of maintaing source when networks were unavailable.
Eric
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Brandon Peterson
Sent: Friday, February 15, 2008 12:24 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] ADTS V6R1 - No SEU updates?
Joe,
I apologize if somebody else addressed this, but I didn't see anything.
LAN console doesn't allow connectivity to the system for your
applications, just the console. In effect you are talking to the
service card via TCP/IP rather than the operating system.
In the end, LAN console is no different than twinax console as far as
the SEU/PDM argument goes. If you are in a situation where you have to
use the console, then you probably can't use RDi.
Brandon
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Wednesday, February 13, 2008 7:02 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] ADTS V6R1 - No SEU updates?
Thierry Bernard wrote:
My interpretation is that V6R1 keywords will be ok but future ones
may not
be.
That's how I understood it as well. The idea is that once there is more
overall acceptance of RDi, they would try to completely wean us off of
SEU. I brought up the fact that some people need SEU as an emergency
technique in case your servers aren't working, but that seems to be less
of an issue as we continue to move away from the twinax console era.
In a LAN console environment, what are the situations where SEU will
work but RDi won't?
Joe
midrange.com
