Thanks to everyone who responded! I have relayed the suggestions and
information from your responses to a group at IBM who is now helping us
with the issue. (Nice of them to do so, since we don't yet own the
product.)
Kelly
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of BMay@xxxxxxxxx
Sent: Monday, April 20, 2009 11:58 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Communications request problems WDSCi
5.1.2andRDi7.5.0
While a 9406 520 should have no problem retrieving information for RDi,
it
also depends on how your partition is configured. Your admin may not
have
given your partition adequate resources. The remote location can also
be
part of the problem depending on what type of connection you have to the
remote site.
It is hard to pinpoint the exact cause without knowing all the details,
but this should point you in the right direction.
HTH,
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
Young i Professionals
http://www.youngiprofessionals.com
"Kelly Cookson" <KCookson@xxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
04/20/2009 11:28 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc
Subject
Re: [WDSCI-L] Communications request problems WDSCi 5.1.2andRDi7.5.0
My laptop should not be the problem. I have a Dual 2.26 GHz Intel Core2
Due with 2G RAM and 112G available on my hard drive after installing
RDi.
I just talked to my system administrator.
I was wrong about being in the same building as our iSeries. We moved
the development partition to a remote box. So the remote connection
might be contributing to communication delays.
Our development partition is on an older box, model 9406 520, feature
7457. The memory has been kept to 3G or 3.5G because we haven't had a
lot of demand for more memory. I'm guessing the performance of our
box\partition may be slowing down communication requests as well.
Our CPU for our development box is usually not high. We get periodically
high CPU at the end of each financial period, but most of the time we
run at fairly low CPU. (My sys admin did not give me exact figures.)
I'm getting the impression that, while we might be able to tune things
to make them a little better, a full resolution might require upgrading
our iSeries hardware and/or moving the development partition back to a
box in the building where our developers work. Is this a correct
impression?
Thanks,
Kelly
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of DeLong, Eric
Sent: Monday, April 20, 2009 10:45 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Communications request problems WDSCi
5.1.2andRDi7.5.0
Ok, though I guess the point I was trying to make was IBM gave us
Code/400 in every version of WDSC they distributed. You could have been
using WDSC 7.0 for the last couple of years, instead of wrestling with
WDSC 5.1.2...
As to the server performance question, can you tell us what
model/release you are connecting? For that matter, what are you using
for a workstation? We have found PC memory to be an inexpensive way to
improve client performance problems.
I suppose it is also possible that your network could be at fault.
There were some releases of where OS400 had trouble auto-negotiating the
Ethernet adapter connectivity parms. Adapters would fall back to 10mbps
from 100mbps, or run half duplex versus full duplex....
Hth,
Eric DeLong
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Kelly Cookson
Sent: Monday, April 20, 2009 9:54 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Communications request problems WDSCi 5.1.2
andRDi7.5.0
Sorry my initial email was confusing. I'm fine with the newly integrated
version of Code Designer in RDi. I was just mentioning Code Designer as
the reason why I did not upgrade versions of WebSphere. I want to
upgrade to RDi.
But these communication request delays are killing me. That's my main
problem.
I'll take the questions I've been getting and ask my system
administrator.
Thanks,
Kelly
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of DeLong, Eric
Sent: Monday, April 20, 2009 9:37 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Communications request problems WDSCi 5.1.2 and
RDi7.5.0
These delays will be primarily related to the performance capability of
your host. In this case, it sounds as though you are accessing an older
iSeries (or even an AS400!). In all cases where I have had these
timeout messages, it is because the host cannot produce the outfile
lists quickly enough. Newer servers (Power5 or Power6) have
significantly better response times...
Re: Code/400 and Code Designer, that tooling was included in all WDSC
packages (up to 7.0), and as long as it is on your workstation, the Rdi
products will see it and permit its use as desired. If you have not
applied updates to the Code/400 product, you *might* want to install the
newest version of Code/400 from the WDSC 7.0 installation disks. That
is the newest version of that product that I am aware of...
-Eric DeLong
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Kelly Cookson
Sent: Monday, April 20, 2009 9:08 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Communications request problems WDSCi 5.1.2 and RDi
7.5.0
Hi.
I have been using WebSphere 5.1.2 for awhile now. I stayed with the
older version to keep Code Designer. I have always had delays in
resolving object table lists, opening source members or copybooks, and
retrieving commands for prompts.
The delays in WebSphere 5.1.2 seem to be related to communication
requests with the iSeries. For example, suppose I am trying to open a CL
source member. I see a message in the lower left corner that says it's
resolving the source member (e.g., "Resolving *LIBL/QCLSRC(MYPGM)
MBRTYPE(*))." The activity bar loops and loops. Then a window pops up
that says: "EVFC9143Q The server is not responding, or the current
communications request is taking a long time. Do you wish to cancel the
request?" When I click the Yes button to cancel, the window disappears
and the object opens in LPEX.
I'm now having the same issues with the trial version of RDi 7.5.0. I
continue to get delays with a window that pops up saying: "EVFC9143 The
server is not responding, or the current communications request is
taking a long time. Do you want to cancel the request?"
What do we need to do to eliminate these communication request delays?
Thanks,
Kelly Cookson
Senior Programmer\Analyst
Dot Foods, Inc.
midrange.com
