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



There are different ways to set the Service Entry Point.
Maybe try a different way:
1) Open the debug perspective, IBM i Service Entry Point view, right click
to set a service entry point
2) Open the debug perspective, IBM i Service Entry Point view, use the
views' menu option to to set a service entry point
3) Create an RSE filter, expand to see your object, right click to Debug
Service Entry, Set Service Entry Point
4) ... maybe others?

On Mon, Oct 23, 2017 at 6:33 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Jon,

I never get into the debug view...

Charles

On Mon, Oct 23, 2017 at 4:16 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

The normal cause for this is that the variables tab is visible in the
debug view, This causes it to refresh values on each and every change in
every variable and for a large program that really slows things down. If
that is the case simply bring the monitors view (or another one) to the
foreground so it doesn't do the refresh.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Oct 23, 2017, at 4:50 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

More info...

After I unsuccessfully set the SEP,
RDi seems to run painfully slow..

When I close RDi, the Java task remains running, trying to restart RDi
gives me a workplace in use error. I have to kill the Java task in
order
to start RDi with my normal regular workspace.

Charles

On Mon, Oct 23, 2017 at 1:48 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

That would not explain why the SEP doesn't appear in the list of
SEPs..

Charles

On Mon, Oct 23, 2017 at 1:05 PM, Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Could it be something as simple as your library list?

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles
Wilt
Sent: Monday, October 23, 2017 2:50 PM
To: Websphere Development Studio Client for iSeries <
wdsci-l@xxxxxxxxxxxx

Subject: [WDSCI-L] SEP not working...

Trying to use RDi to debug via SEP on our production box instead of
the
green screen STRDBG...

I add the SEP, but it doesn't appear to be being set. Not shown in
the
list of SEPs and RDi doesn't switch to the debugger when I call the
program.

Verify connection shows:
Connection to Central service . . . . . . . . . . . . .successful
Connection to Command service . . . . . . . . . . . . .successful
Connection to Data Queue service . . . . . . . . . .successful
Connection
to File service . . . . . . . . . . . . . . . .successful Connection
to
Record Access service . . . . . . .successful Connection to Signon
service
. . . . . . . . . . . . . .successful Checking PTFs Rational
Developer
for
i . . PTF missing Remote System Explorer . . successful IBM i
Integrated
Debugger . . PTF missing Product 5770SS1 found PTF SI57638 successful
PTF
SI63271 successful Required PTF SI63708 is missing PTF SI60383
successful
Checking server callbacks Checking callback to RSE daemon Callback to
10.134.52.5 on port 4300 successful

The missing PTF doesn't seem to explain the failure....

I suspect it's network/security related, but I'm at a loss as to what
to
request be opened up...

Note that debug server is started. In fact, when I ended it, I saw a
message in RDi saying something along the lines of "server required
for SEP
is ending"..

Any thoughts?

Thanks!
Charles
--
This is the Rational Developer for IBM i / Websphere Development
Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a
message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list
options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development
Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.



--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.