×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
To attach the RDi debugger to a running job:
1. In the Remote Systems view, expand system->Jobs
2. Either user an existing Jobs filter or create a new one
3. Expand filter->subsystem to find the job
4. Right-click -> Debug As -> IBM i job
It comes in handy to debug a job sitting at a Message Waiting status.
-----Original Message-----
From: Buck Calabro [mailto:kc2hiz@xxxxxxxxx]
Sent: Friday, October 19, 2018 10:29 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDI 9.6.0.4 Debug does not work, fall back to Green Screen... AGAIN...
On 10/19/2018 10:44 AM, Ken Killian wrote:
Using RDi 9.6.0.4 and the debug break points do NOT work. Apparently, RDI cannot stop at an internal stored-Procedure.
Just minutes ago I debugged an internal RPG sub-procedure with RDi 9.6.0.4. The debugger stopped on the breakpoints as expected.
I vaguely recall that you often attach the debugger to an already executing program. I can't say that I ever did that - I always start SEP, then execute the program, then when the debugger stops at the first line, set the breakpoints I want. Maybe this is the difference?
When colleagues' debug sessions don't stop at breakpoints, it's very often the case that the program that is running is either
a) different library than the debugged program (including QRPLOBJ)
b) different user profile than the SEP
--
--buck
http://wiki.midrange.com
Your updates make it better!
midrange.com
