Re: Debugger, debugger, where art thou?

It looks like the debugger is waiting for your batch program to run so 
that it could attach to it.

Could you please check to see if your batch program is still in queue?

One other thing you could try is to use the service entry point.  Right 
click on your program in RSE, and choose Debug (Service Entry) -> Set 
Service Entry Point to set a service entry point on that program.  And 
then just invoke the program you normally do.  For example, submit it to 
batch, call it in the 5252 session.  A debug session should come up with 
your program under debug.

Thanks,

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





"albartell" <albartell@xxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
11/21/2006 02:04 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
[WDSCI-L] Debugger, debugger, where art thou?






Ok, so I was really excited that I got the debugger working today as I 
found
the debugging profiles make it really easy to start debugging with the 
click
of a button - great for iterative development.
 
Then I started having troubles with the LPEX editor (different issue) so I
restarted WDSC.  Now I can't debug anymore!  I select the previously 
defined
debug profile and it gets "stuck" at a certain point.  Below is a screen
shot of the Debug pane
 
http://mowyourlawn.com/temp/wdscdebug1.jpg
 
I have ensured the Remote Server "Debug" is running:
http://mowyourlawn.com/temp/wdscdebug2.jpg
 
There are no errors in <wdsc6.0 base>\.metadata\.log
 
I have even gone as far as shutting down TCP and restarting (i.e. ENDTCP 
and
then STRTCP from the console).
 
I have tried creating a new debug profile in case there was a problem with
the other one - no luck.
 
Is there another place I can look?
 
 
Aaron Bartell
http://mowyourlawn.com