Re: WDSC Debugger WRKACTJOB MSGW

Is there any reason you can use the iSeries Jobs subsystems for your job

management needs? 

Assuming you meant "cant" instead of "can"....

I can use them just fine, but it seems like quite the disconnect.  If I
start a debug invocation in WDSC and wait for it to start, and if it hangs
at a certain point I have to go job hunting in WRKACTJOB and see what is
wrong. Or for that matter I have to go hunting period and 'debug my debug'
to see what is wrong with WDSC. That just seems like something I should be
able to do right from WDSC.  Maybe something like being able to right click
on a debug session and see what "state" it is in or see the job log of the
iSeries job it is being tied to.

I guess if nothing else you now have a little more information as to how the
debugger is first perceived by somebody who hasn't really used it much (me)
and what I had to do to "figure it out".

Thanks for your response,
Aaron Bartell
http://mowyourlawn.com

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Violaine Batthish
Sent: Wednesday, November 22, 2006 9:16 AM
To: Websphere Development Studio Client for iSeries
Cc: 'Websphere Development Studio Client for iSeries';
wdsci-l-bounces@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] WDSC Debugger WRKACTJOB MSGW

Hi Aaron,

Is there any reason you can use the iSeries Jobs subsystems for your job
management needs?

As for the binding errors, its on our list of requirements.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab