Re: iSeries Service Entry Point failing -- WDSCI-L

Xuan,

If I remember correctly I set the service entry point monitored a few
variables, made a few changes, recompiled, refreshed, monitored again,
made another change , recompiled - got an error on compile, fixed the
error, recompiled sucessfully and the I think when I tried to refresh
after the the sucessful compile the program did not enter debug mode
when I called it from the green screen.  In total it might have been 3
or 4 calls/debugs before the failure.

Mike

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Xuan Chen
Sent: December 15, 2006 3:52 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] iSeries Service Entry Point failing

It will be nice if someone could have some fixed scenario to reproduce
this problem. 

How many times you debug the program before the SEP failed?

Thanks,

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





"Mike Roderick" <Mike.Roderick@xxxxxxxxxxxxxxx> Sent by:
wdsci-l-bounces@xxxxxxxxxxxx
12/15/2006 02:18 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<WDSCI-L@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] iSeries Service Entry Point failing






Just today I experienced the service entry point failing (I never
noticed a problem before)

I ended the Debug server and restarted it.  Then I reset my service
entry point and it worked.

No amount of refreshing or adding and removing the service entry point
prior to restarting the server was working...

Mike 

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of smorrison@xxxxxxxxxxxxxxxxxxx
Sent: December 14, 2006 1:47 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] iSeries Service Entry Point failing

I just encountered a problem with the debug function not working. I
resolved it be ending the QB5PHSRV job and stopping and restarting the
debug server. The process that caused the problem is that I started the
debug server in WDSC yesterday. At the end of the day, I signed off and
ended my Client Access sessions and logged off my PC, but didn't shut it
down. This morning, I restarted the debug servers in WDSC, and selected
a program for debug, but  the program failed to stop at breakpoints.
This happened several times, and I refreshed the breakpoints after
recompiling the program. Eventually I ended the QB5PHSRV job. I then
attempted to restart the debug server, but this was grayed out, until I
first stopped the debug server. Stopping the debug server threw up a
communications error message, but then allowed me to start the debug
server, and after reselecting the program for debug, the breakpoints did
work.

Hopefully you can recreate the problem from this description. Let me
know if you need additional information.\

Steve

Steven Morrison
Fidelity Express
903-885-1283  ext. 479



smorrison@xxxxxxxxxxxxxxxxxxx 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/13/2006 03:42 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] iSeries Service Entry Point failing

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?


I have also experienced the problem of the SEP no longer working. In
these 

cases, there have been no error messages, but no debug session comes up 
when the program is called. I have tried refreshing the SEP in the
Service 

Entry points dialog, with no results. I generally end up stopping and 
restarting the WDSC. This hasn't occurred often enough to isolate the 
actions which cause this problem. I'll remember the tip listed elsewhere

of ending the QB5PHSRV job.

Steve

Steven Morrison
Fidelity Express 
903-885-1283  ext. 479