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



Thanks Yuan, I will do the PMR. I was not aware of the "Clear all service entry point" option though.

Paul Therrien
Orion South, Inc.
504-374-9551
800-437-7173; Ext. 551
ptherrien@xxxxxxxxxxxxxxx


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Xuan Chen
Sent: Tuesday, November 20, 2012 3:41 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDP 8.5 and Service Entry points - reset of a program/debug


Hi Paul,

The steps you did sounds correct to me. Once you re-compile your program, you should right click on the SEP in Service Entry Point view, and choose Refresh. Remove and reset will not work. Does this problem happens all the time? Could you please open a PMR so that we can look more into it?

For now, one way to workaround this problem is to click on a drop down in the right top corner of the Service Entry Point view, and choose "Clear all service entry point -> ConnectionName" to reset the Service Entry Point engine job. And then set the SEP again.

Thanks,

Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx





Paul Therrien
<ptherrien@reagan
power.com> To
Sent by: "wdsci-l@xxxxxxxxxxxx"
wdsci-l-bounces@m <wdsci-l@xxxxxxxxxxxx>
idrange.com cc

Subject
20/11/2012 03:30 [WDSCI-L] RDP 8.5 and Service Entry
PM points - reset of a
program/debug

Please respond to
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>






How do you get RDP Service Entry points to reset/restart once a program has been recompiled?
I have had a gnawing issue for a while...

1. Set a service entry point on a program

2. Run the program

3. Debug in RDP thanks to the service entry point until logic error
is determined

4. Find code that needs to be changed and fix it.

5. Recompile the program

6. Refresh the service entry point (or even delete the service entry
point and reset it)

7. Run the newly compiled version of the program

8. However ... I no longer can get the RDP debugger to kick in on the
service entry point.



In this scenario, the only way I have been able to get the service entry point debugging to work is exit RDP and restart.

There must be a better way.

Can anyone have any offer any tips for this?




Paul Therrien
Orion South, Inc.
504-374-9551
800-437-7173; Ext. 551
ptherrien@xxxxxxxxxxxxxxx<mailto:ptherrien@xxxxxxxxxxxxxxx>

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