Re: Cannot Start Debugging

Are you using a VPN or SSL proxy? I seem to remember needing to launch
WDSC (Rdi) before starting the SSL proxy, since the RSE callback daemon
has to acquire port 4300 before the proxy started. Perhaps this is
unique to the SSL VPN that we use. This is one reason I never use the
STRRSESVR.

http://publib.boulder.ibm.com/infocenter/iadthelp/v6r0/index.jsp?topic=/
com.ibm.etools.iseries.rse.doc/tasks/ttrouble5.htm

-Eric

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Chamara Withanachchi
Sent: Tuesday, December 22, 2009 11:25 AM
To: Websphere Development Studio Client for iSeries
Cc: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Cannot Start Debugging

Yes I have allowed this port from my firewall and even in my personal
fire wall but still the same.


--

Regards
Chamara Withanachchi

IBM certified Syatem i Specilist
RPG Programmer
(Owner of www.RPGIV.info)

+ 971 505698644



Sent from my iPhone

On Dec 22, 2009, at 7:49 PM, "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
wrote:

Do you run Windows Firewall or some other PC security software on your
workstation? The connection to port 4300 would be blocked by most
(all?) firewall products, I think.

I never use STRRSESVR. For debug, simply STRDBGSVR to start the debug
server, and use SEP to launch the debug session.

Hth,
Eric DeLong

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-
bounces@xxxxxxxxxxxx]
On Behalf Of Chamara Withanachchi
Sent: Tuesday, December 22, 2009 3:27 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Cannot Start Debugging

Hi,

I was trying to debug from my WDSCi but when i Start the debug server
(STRRSESVR NAME(DR)) from my 5250 screen it's giving following
message.

Error connecting to Remote Systems Explorer

Message ID . . . . . . : RSE2001 Severity . . . . . . . : 30

Message type . . . . . : Information

Date sent . . . . . . : 22/12/09 Time sent . . . . . . :
13:24:58



Message . . . . : Error connecting to Remote Systems Explorer

Cause . . . . . : The STRRSESVR command could not create a TCP/IP
connection
to the Remote Systems Explorer (RSE) at remote location 10.10.16.199
on
port
4300. Possible causes: The iSeries RSE communications daemon has not
been

started on the client. The remote location name is not a correct
TCP/IP

hostname or address. The iSeries RSE communications daemon is
listening
on
a different port number. Start the iSeries communication daemon and
verify

that the remote location name and port are valid.




My RSE communication port is set to 4300. and I can do compilations
from
WDSCi

Please guide me what I'm missing and what is my mistake.


--
Regards,

Chamara Withanachchi
IBM Certified Power System Expert
RPG Programmer
(owner of www.rpgiv.info)

WWW.RPGIV.INFO
Mob: +971 50 5698644
Tel: +971 6 5595887
chamaraw@xxxxxxxxxx

i want to be future ready. i want control. i want an i.
--
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.


--
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.