Re: Extracting debug view

Hi, Reeve, Jon and Vern,

After some googling around, I recalled the name "Alex Nubla" and found this:

    https://geocities.restorativland.org/SiliconValley/Pines/5581/tips.htm ;

It is a copy of the old (long gone) "A S 4 0 0 J O U R N A L" web site ...

Search on that page for "RTVILE" and you will find the a that Alex created that retrieves "debug source" for ILE programs compiled with DBGVIEW(*LIST) or DBGVIEW(*ALL).   

Just be aware that the file inside the zip file is not a normal save file, so be sure to read the "read.me" file for instructions on how to restore the contents.

Hope that helps,

Mark S. Waterbury

On Sunday, June 13, 2021, 01:43:30 PM EDT, Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

Seems RtvSrc was published awhile ago -RETRIEVING RPG SOURCE NEWS/400 published utility Retrieve Source (RTVSRC), which retrieves source from ILE programs, in September 1997 - I have a CD with iSeries stuff from 2000-2005, don't know if it's on there, have to get an external CD/DVD drive for my new laptop. Then I'll look.

Vern

On 6/13/2021 10:37 AM, Jon Paris wrote:
https://www.ibm.com/support/pages/how-retrieve-rpg-ile-source-when-compiled-debug-view-all-or-list <https://www.ibm.com/support/pages/how-retrieve-rpg-ile-source-when-compiled-debug-view-all-or-list>

There is also a program RtvSrc that is out there in the wild somewhere although a quick look-see with google did not locate an active link for it.


Jon Paris

On Jun 13, 2021, at 1:35 AM, Reeve <rfritchman@xxxxxxxxx> wrote:

Greetings all--

I'm trying to solve a customer problem and we'd like to extract the
DBGVIEW(*LIST) source so we can compare it to the current QRPGLESRC
(restoring from the previous day's backup won't help; that source was clean
and multiple programmers have meddled with the code, unsuccessfully, to
find/address the problem).  This is more of a forensic exercise for the
management team--they like to see a post-mortem/hot wash/after-action
report whenever we have incidents (which, fortunately, is seldom).

I'm not kidding when I say we think the programmer's cat walked across the
keyboard.

Is there a free tool, API, or published procedure to do this?  I expect
I'll have to do quite a bit of cleanup to remove generated SQL and that's
fine.  Getting the recovered code into a source member and jumping on
iSphere's extremely handy source compare we give us our answer.

I'd prefer the extraction approach instead of writing a macro that does a
text screen shot, appends it to an open document, and then reruns the
macro.  While this works 99.99% of the time, we can't risk the possibility
of missing what's likely a very subtle error because of a defective debug
view process (we already have one defective process, which is why I'm doing
emails at 10:30 PM Saturday night).

Thanks,
Reeve