Re: Service Entry Points

+1, Most of the time, I use the Green Screen debugger. It works!


From: Lorne<mailto:lorne.sturgeoff@xxxxxxxxx>
Sent: Tuesday, May 5, 2020 12:02 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Service Entry Points

Same here, since the early days of WDSC. I've opened tickets with IBM in
the past and even spoke to IBM developers at our local user group meetings.
None of the developers here will use the RDi debugger except for trivial
cases. Nobody wants to risk spending a lot of time setting up a test only
to have the program run to completion without breaking for the SEP. It
works great when it works. Too often it lets me down and often at the worst
possible time.
Lorne.

On Mon, 4 May 2020 at 18:40, DFreinkel <dfreinkel@xxxxxxxxxxxxxxxxx> wrote:

I have always experienced this problem and have not been able to resolve
it. I have had to restart the debug server and rdi to get it going again.

In the end I have resorted to using the system debugger included in ACS
and iAccess. It’s reliable and just as good. Only issue has been an
inactivity timer around the 2 hour mark. I just reconnect and go again.

Darryl Freinkel

--
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@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com