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



Yes. DBGVIEW(*NONE) COMPILEOPT('DBGVIEW(*LIST)')

I know it looks weird. . . but give it a go. You'll not be sorry.

"Richard Reeve" <richreeve@xxxxxxxxx> wrote:

I appreciate all of the kind advice from you all.  Unfortunately, the
only debug view options that I have are *source and *none......

Richard Reeve


________________________________
From: Dennis Lovelady <iseries@xxxxxxxxxxxx>
To: 'RPG programming on the IBM i / System i' <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, May 3, 2011 6:48 PM
Subject: RE: Strange acting program in debug

Actually, (at least at V5R3) you cannot do that, directly.  Not sure
which
OS level Richard is using, but at V5R3, here's what I do, using PDM:

14 next to member to be compiled
On command line, type:
DBGVIEW(*NONE) COMPILEOPT('DBGVIEW(*LIST)')

(you could put "*ALL" there, I suppose.)

Press ENTER.  Voila!

(Which reminds me... anyone heard from David Foxwell lately?!?!)

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"If you can keep your head when all about you are losing theirs, it's
just
possible you haven't grasped the situation."
        -- Jean Kerr


Richard:

Try specifying DBGVIEW(*ALL) on your compile command and I think you
will find it will work much better.

HTH,

Mark S. Waterbury

  > On 5/2/2011 7:43 PM, Richard Reeve wrote:
So, I have this large (20k + lines) program that has me perplexed. 
I
made some minor changes to a subroutine.  When testing, it did not
perform as desired, so I put in debug.  This is where it gets very
strange....The subroutine builds an SQL statement.  Then, as I step
through in debug, the next statement is an SQL prepare - but instead
the program goes to a subroutine that isn't even referenced in the
subroutine from which it came.  It then goes through a few lines and
oddly returns to the subroutine where it began (although not where it
left off).  My initial thought was source/object mis-match so I
recompiled, signed off&  on and tried again, only to have the same
result.

I have consulted with 4 programmers in house but we are all
stumped.
Does this sound familiar to anyone?  Any suggestion/ideas would be
much
appreciated.

Thanks.

Warmest Regards,
Richard Reeve
--
This is the RPG programming on the IBM i / System i (RPG400-L)
mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.