RE: RSEF1002E when trying to open RPG member withRemoteSystems LPEX Editor -- WDSCI-L

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

Subject: RE: [WDSCI-L] RSEF1002E when trying to open RPG member withRemoteSystems LPEX Editor
From: "Sean Porterfield" <sporter@xxxxxxxxxxxx>
Date: Mon, 29 Sep 2003 11:24:44 -0400
Importance: Normal
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

> From: Bob Cagle

> So, did this correct your problem with the RSE connection in WDSCi?


Yes, I needed to allow port 446 for DRDA.  I don't know if it used DDM or
not, but I allowed ports 447 and 448 just in case.  I just opened a source
member now and port 446 is the only new connection.

As an Amazon Associate we earn from qualifying purchases.

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.