RE: RDi Debug - RSE2001

[Dave Begley <Dave.Begley@xxxxxxxxxxxxxxx>]

Thanks for the info.  I found a way to use RDi debug with service entry points and avoid STRRSESRV altogether.  That method is quicker and cleaner.

Dave Begley
Programmer

602 Virginia St. E.
Charleston, WV  25301
304.353.8763
dave.begley@xxxxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Wednesday, November 16, 2016 9:59 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: RDi Debug - RSE2001

Error message RSE2001 will tell you the port needed.  The remote network support people will need that.  See also:
https://www.ibm.com/support/knowledgecenter/SSAE4W_9.5.1/com.ibm.etools.iseries.troubleshoot.doc/topics/rse/ttrouble5.html
The system will also need to be able to find the IP address of your PC.
Hopefully a PING from the IBM i can find your PC.  Although the ping may fail since network administrators tend to block many useful debugging features (like PING) out of a general fear that they can be used for a Denial Of Service attack instead of just figuring out how to allow ping but still prevent it from being destructive.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   Dave Begley <Dave.Begley@xxxxxxxxxxxxxxx>
To:     "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>
Date:   11/16/2016 09:47 AM
Subject:        RDi Debug - RSE2001
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I sent a ticket into our systems folks but I thought I would ask here
also.  When I issue the STRRSESVR command I get an error RSE2001.  I found
some information on the internet but I couldn't figure out what to try.

It started after we upgraded to a new system that is housed and run by a
3rd party.

Let me know if anyone has had this and solved it.

Thanks.

Dave Begley
Programmer
[cid:image003.png@01D1542E.76747EF0]
602 Virginia St. E.
Charleston, WV  25301
304.353.8763
dave.begley@xxxxxxxxxxxxxxx<mailto:dave.begley@xxxxxxxxxxxxxxx>




Disclaimer: This communication and any files transmitted with it may
contain information that is privileged, confidential and/or exempt from
disclosure under applicable law. If you are not the intended recipient,
you are hereby notified that any disclosure, copying, distribution, or use
of the information contained herein (including any reliance thereon) is
strictly prohibited. If you received this communication in error, please
immediately contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.



Disclaimer: This communication and any files transmitted with it may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this communication in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.