Re: Extracting debug view

Hi

In the STRDBG session, some of the source can be off the screen to the right - just thinking you might have needed to press F20 to see that part.

DMPOBJ, if you have authority to use it, will have the source in 16 or 32 columns - it's in a SPLF, so it can be converted to PDF or something and you can copy-paste more easily.

Cheers
Vern

On 6/13/2021 5:56 PM, x y wrote:

Further update: worked fine, almost: the STRDBG (with apologies) view
dropped a closing parens at the end of the source line on a complex SQL
statement and so the recovered source failed to compile. I checked my
original source and confirmed the parens is in the source and not in the
debug view.

The debug server crashed a few times but I suspect the customer isn't
current on PTF's. Just another weekend...

On Sun, Jun 13, 2021 at 4:25 AM Art Tostaine, Jr. <atostaine@xxxxxxxxx>
wrote:

iACS debug view lets you copy the whole source.

On Sun, 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

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