× 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.



Planet of the Apes wrote:
I used STRDBG to set a breakpoint in the RPGIV program, then used STRSQL to execute the UDF, but it wouldn't stop at the breakpoint.

Yeah, that's because there's threading involved. The FAQ describes how to debug a UDF http://faq.midrange.com/data/cache/185.html but I guess the same thing is in the IT Jungle article. I apologise for not being very clear.

BTW, I'm using WDSC these days and I also tried without success to debug it by setting a Service Entry Point from WDSC to debug it. I was able to set an SEP on the program, but it wouldn't start debugging the program in WDSC when I was using STRSQL on the green-screen session. I guess I need a tutorial in debugging with WDSC...

WDSC 7.0.0.2 here. I opened the RPGLE program that makes up the function, but that's because I wanted to edit it anyway. In the filter/navigator view, right click the member name and choose 'Debug (Service entry)' then 'Set service entry point' Once I get the acknowledgment that the SEP was added, I go to a green screen or the iNav SQL script panel and run the SQL that invokes the UDF. WDSC takes a moment to switch to the debug perspective and then shows the RPG source. F5 to step into, and if you're like me you'll accidentally press F11 a few times to look at a variable's contents. Hover the cursor is better because F11 tries to fire up my last Java mess for debugging...
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.