Re: Extracting debug view

[x y <xy6581@xxxxxxxxx>]

My thanks to all who offered code and suggestions.  RTVILESRC is a winner.

It's been a long time since I found a problem but I'm confident there's a
small bug somewhere in the V7R2 compiler.  The parens in column 81 did not
make it into DBGVIEW(*LIST) and this caused me some heartburn (a look at my
archived source highlighted the problem):
 ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7
...+... 8 ...+.
                      (gpdfrtype = 'ZIP' AND sps020(:conspostal, gpdfrval)
= '1')

DMPOBJ confirmed the closing parens is missing in the object.  In my RDi
"Free-form SQL Formatting" panel, "Treat text beyond column 80 as SQL code
to be formatted".is checked.

The SQL preprocessor created this:
... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+... 8
...+... 9 .
  //*               (gpdfrtype = 'ZIP' AND sps020(:conspostal,
gpdfrval)='1

...which is missing two characters.  The program compiles and I wonder if
there's an automatic CAST taking place (converting the number 1 to a
literal '1')...but the closing parens isn't there and I am stumped.

Normally I let RDi reformat the SQL but I formatted this code manually to
improve readability; it appears I missed this one.  I wish RDI's SQL
formatter had a few more options...or I need to find an RDI plug-in.

17 hours is enough for one day.  Out.



On Mon, Jun 14, 2021 at 2:27 AM Thomas Raddatz <thomas.raddatz@xxxxxx>
wrote:

> In order to complete the list of utilities, iSphere adds option "Display
> Module View" to the context menu of objects of type *MODULE.
>
> Thomas.
>
> -----Ursprüngliche Nachricht-----
> Von: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von Reeve
> Gesendet: Sonntag, 13. Juni 2021 07:35
> An: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
> Betreff: Extracting debug view
>
> 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