Dumb debug question of the week.

  My guess is that you cannot have the debugger see anything like a
DLYJOB CL command or a DSPF wait, since these are low level system-type
tasks that the debugger will not see.  The debugger wants to go against
executing calc lines.  You have to put a debug point on a real executing
line, even if you have to condition it. 

  A better method (from the green screen debugger) may be to SETATNPGM
QCMD, then start running your interactive session.  Once you are deep
into the app, and when you get to some EXFMT before the section you want
to debug, press the Attention key (the Escape key on a PC keyboard).
Then from the command line that displays, you can the STRDBG cmd or use
DSPMODSRC to set debug points within the program.  And you're off to the
races.

 You might want to put the debug point on the CALL to your "Long Wait
Pgm".  That should be an executable line.


-----Original Message-----
From: code400-l-bounces@xxxxxxxxxxxx
[mailto:code400-l-bounces@xxxxxxxxxxxx] On Behalf Of
code400-l-request@xxxxxxxxxxxx
Sent: Wednesday, December 21, 2005 1:00 PM
To: code400-l@xxxxxxxxxxxx
Subject: CODE400-L Digest, Vol 3, Issue 36


Send CODE400-L mailing list submissions to
        code400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/code400-l
or, via email, send a message with subject or body 'help' to
        code400-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        code400-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of CODE400-L digest..."


Today's Topics:

   1. Dumb debug question of the week. (Bob Anderson)


----------------------------------------------------------------------

message: 1
date: Wed, 21 Dec 2005 08:02:37 -0500
from: "Bob Anderson" <banderson@xxxxxxxxxxxxxxxxxxx>
subject: Dumb debug question of the week.

Good Morning,
        My mind is just not making the connections this morning.

I have an interactive session going that I want to debug. The job has a
call to a program called DBGwait which puts it into a wait state. When I
start My iSeries Distributed Debugger it just keeps sitting there when I
give it the job name of my interactive session.  

        The program has been compiled with *SRCDBG 

Anybody have a clue what I am doing wrong

Thanks


Bob Anderson 



------------------------------

_______________________________________________
This is the CODE/400 Discussion &amp; Support (CODE400-L) digest list To
post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries discussion has its own mailing list. Information
can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsci-l

End of CODE400-L Digest, Vol 3, Issue 36
****************************************