Re: Extracting debug view -- RPG400-L

I found a link on COde400.com that includes something from someone with user name JonBoy - https://code400.com/forum/forum/iseries-programming-languages/rpg-rpgle/149198-recovering-lost-rpg-source

There's a 2018 link by that fellow to www.juggersoft.com - they seem still to be in business, although the site uses Flash, so stuff doesn't all work. Still, there's a pricelist.

On that page someone also mentions DMPOBJ, which might be the basis of RTVSRC, cuz when compiled with *LSTDBG or DBGSIEW(*LIST or *ALL), the source is in the object whole.

HTH
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
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com