Re: Program stops for SEP, but debug doesn't start in RDi

I love SEP's, but IMO they're the most flakey thing about RDi. For me, this issue here is the least frequent problem I see. iNav shows the job "Waiting for event" as expected, but debug never starts in RDi. My work-around is to bounce the debug server. That releases the job, which continues normally. I only have one co-worker who uses RDi, so the restart doesn't cause too many problems.



-----Original Message-----
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Thursday, December 01, 2016 4:04 PM
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Program stops for SEP, but debug doesn't start in RDi

I was successfully debugging a program via SEP earlier in the day.

However, now when I run the program, it halts (I think) but never comes up in RDi debug.

I'm pretty sure it's halted, since the call stack has as a last entry
QTESEPEH QSYS /01E3

and it doesn't change nor does any file I/O take place.

I'm removed and re-added the SEP.
Restarted RDi...
Signed off and back onto the 5250 session.

Any thoughts as to what is going wrong or where to look for that answer?

Running RDi 9.5.1, program is on a 7.2 box.

Thanks!
Charles