Re: DBGVIEW(*STMT) as default for ILE RPG compilation

Say you send a program to someone but don't want them to be able to see

your code through a source or listing view. If it has a statement view, you
can still debug it on their system if you have your listing.

I had never thought of it in this way. I think I know have a use for
*STMT! Thanks Barbara!

Aaron Bartell
http://mowyourlawn.com

On Thu, Jun 19, 2008 at 7:55 PM, Barbara Morris <bmorris@xxxxxxxxxx> wrote:

James Lampert wrote:

Just out of morbid curiosity (and with no hostility):

Does DBGVIEW(*STMT) actually serve any useful purpose? It always seems
to me that if I do a STRDBG on a program that was compiled with this
default value, it brings up the ILE source level debugger, with no
source, and no obvious way to do anything.

Some level of debug view is necessary to support the formatted dump. If
I recall correctly, it's because of the formatted dump that ILE RPG and
ILE COBOL default to the statement view rather than defaulting to *NONE.

It's possible to debug from the statement view, but you pretty much need
to have a listing available. It's almost as awkward as the old strdbg +
addbkp + dsppgmvar, brrr.

Say you send a program to someone but don't want them to be able to see
your code through a source or listing view. If it has a statement view,
you can still debug it on their system if you have your listing.

--
This is the RPG programming on the AS400 / iSeries (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.