Re: Debugger, debugger, where art thou?

From you note, I assumed that you used Debug as -> Batch context menu.

Could you please try the following:
Right click on the program you want to debug, and choose Debug (prompt) -> 
Batch to invoke the the debug launch config dialog.
Switch to How to start page, and see what is the command you used for 
invoking your application.  Is it the right command?

For batch debug, the default is command just the SBMJOB (CALL ) command. 
You probably need to update the command to include the right parameters.
Once you change it, you could save the launch config to a specify name to 
save it, and invoke it later on.

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 03:02 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] Debugger, debugger, where art thou?

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

I do a WRKJOBQ *ALL and watch the job get queued up and leave the queue by
hitting F5 repeatedly.  So it appears to be getting that far.

The Debug (Service Entry) approach worked!  Whoo hoo!  So what can I look 
at
next to see why it doesn't work when I invoke it directly from WDSC?

Thanks for your help Xuan,
Aaron Bartell

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] 
On
Behalf Of Xuan Chen
Sent: Tuesday, November 21, 2006 1:22 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] 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