Re: Communications request problems WDSCi 5.1.2 and RDi 7.5.0

Kelly,

Ah, yes, my favorite message box... I think someone else has mentioned that it's related to the responsiveness of your System i/iSeries/AS/400 or whatever. Yes, it is. We have several 'machines' (partitions, actually). I can count on seeing that message frequently on our development machine, which is normally overloaded and is not tuned well for client/server. It's rare when I connect to the production box that I have access to. Unfortunately, I'm supposed to work on the dev box most of the time.

When I work remotely via VPN, I get the message a little more often, but not a lot more, really. It's mostly the responsiveness of the box that matters. I suspect that some tuning would go a long way to reducing the issue, but I don't have access to the controls and the people who do don't have time to mess with it. I don't know what your situation is, whether you have someone with the expertise to tweak your i, or if tweaking it would help. I suspect the main options are tuning, upgrading hardware, and living with it. Me, I have to live with it. I hope you have something better!

Dave Shaw
Mohawk Industries

----- Original Message ----- From: "Kelly Cookson" <KCookson@xxxxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, April 20, 2009 10:08 AM
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?