WDSC Debugger WRKACTJOB MSGW

So I am finally able to start using the debugger as I now own a machine with
all of the correct PTF's - whoo hoo!
 
I started debugging my first application by simply going in and selecting
debug on the pgm object I wanted to debug.  I tried this multiple times
without success as it got to a certain point and just kept hanging.  As I
was giving up on the debugger I checked WRKACTJOB to find the following job:
 
Subsystem/Job  User        Type  CPU %  Function        Status
QBASE          QSYS        SBS      .0                   DEQW 
  QDFTJOBD     AARON       BCH      .0  PGM-TESTRJLMSG   MSGW 

In it was an error basically stating I had forgotten to prime the debug with
input parms for the program call - doh!  So that was easy enough to fix, but
now I find myself constantly going back and forth between the WDSC debugger
and WRKACTJOB to get information as to whether the program has bombed or
not.  Is there a better way?  Do I have something in my environment setup
wrong?
 
This ranks right up there with compiling a program in WDSC that has binding
errors - doesn't tell you what they are so you have to go back to green
screen to figure it out - very annoying.
 
Thanks,
Aaron Bartell
http://mowyourlawn.com