× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WDSCI-L
  3. August 2004

Re: RSE server not working part 2

David, do you have authorization to call IBM Support? Does your company have Support Line? If so, I suggest you call them - they are really very good, once you get past the initial contact. ;-( There's a registration process you probably need to go through to have access - it can be on the Internet or someone at your company may have the process down. Or if you go through a business partner, find out how it is done.

HTH
Vern

At 01:46 AM 8/5/2004, you wrote:
Yesterday's post:
Hi, i'm using WDSCi 5.0 and recently got an new computer with windows 2000 sp4 on my desk.

I installed WDSC on it and configured the usual stuff . After a few days of coding I noticed that I cannot
run interactive task because I cannot get the RSE server running.
Just I few days ago, everything worked just fine on the other machine so it has to be something on this
machine. The other machine was on win2000 and sp3. So i'm guessing the sp4 is the problem.

If I start the RSE server I get the "Connection name not ... " or something like that.
Then when I enter the exact command again the process says "Starting RSE ..." and then nothing
happens for a while and after a couple of minutes I get "SOCKET ERROR"

I don't understand what's wrong. Can somebody help me?

I used an network sniffer to see what's going wrong. But I'm not a TCP/IP expert and maybe
someone in the mailinglist is. I attached the tcp/ip log to this message.
The log is from the point where i have requested an interactive call and websphere asks me
to start a rse-server in an client access. I type the command (STRRSESVR name(<name>)) and hit enter.
Then I get the "connection name not defined" (WHICH IS). That's were the log stops.

<<tcp.log>>
I have contacted the iSeries admin and he said nothing changed there since the last time it worked. So
the problem is the machine i'm working on.
_______________________________________________
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.