Re: iSeries Service Entry Point failing

Justin,

Could you please tell me what happened when your SEP "stops working"?  You 
cannot set the SEP any more, or you run the program, but no debug session 
came up?

Instead of ending the debug server, one other thing you could do to 
recover is to find out the server job which process you service entry 
point.  You could do that by looking into your QUSRWRK subsystem, and find 
a job called QB5PHSRV (under your user profile), and see if anything wrong 
with that job.  And you could end that job if necessary without 
distracting other programmers.  But I want to know why in some cases it 
failed.  Could you please send me the information of that job once you 
could recreate the problem (like job log, call stack, etc).  Thanks.

Thanks,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx





"Justin Taylor" <JUSTIN@xxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/13/2006 03:39 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] iSeries Service Entry Point failing






I use iSeries Service Entry Points extensively.  For some reason that I
have been unable to determine, they periodically stop functioning.  I
try to Remove and re-Set them but that fails to make a difference.  In
the past I would stop and re-start the Debug server (via the Remote
Systems view) and that would always solve the problem.  We now have
multiple developers using WDSc, so I can no longer just bounce the Debug
server whenever I need to. 

Is there something else that I can do to get the iSeries Service Entry
Points to start working again?