Re: Debbugging an already runnign program

Thanks... that's good information. I think my problem may have been some kind of quirky disconnect within RDi debug. I couldn't get debug to work on another program when I set a service entry point, then called the program.

I ended up completely restarting RDi... then debug worked fine using both methods.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: Monday, May 04, 2015 8:31 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debbugging an already runnign program

When you debug something running and it's waiting on some form of
IO--QRCVDTAQ, display-file read, etc., first you attach to the program (as
you've done). Then you need to "Suspend" the program: it's the little
pause button in the program controls. Then when the IO completes, you can
start to step through the program. A breakpoint on the statement
immediately following the IO should also serve your purpose.

IIRC, I usually click the "Suspend", then "Step {Into/Over}". When the
input statement completes, it will process a step and stop again.

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 05/02/2015 01:00:03 PM:

From: wdsci-l-request@xxxxxxxxxxxx
----- Message from Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
on Fri, 1 May 2015 19:50:37 +0000 -----

To:

"'WDSCI-L@xxxxxxxxxxxx'" <WDSCI-L@xxxxxxxxxxxx>

Subject:

[WDSCI-L] Debbugging an already runnign program

So I have a program running that is sitting on a statement QRCVDTAQ.
(data queue wait is -1). I wanted to debug the program.

So in RDi, I located the program und my active jobs... right clicked
and selected "Debug" then "IBMi Job". It jumped right into the
program at the statement. But it did not allow me to step through
the program when something was written to the data queue. Do I have
to set a breakpoint since the program is running?

I know for certain that this program received & processed based on
the job log entries.

Thanks,
Greg