RE: Regarding DBGVIEW(*STMT) in CRTBNRPG

Bob,

Just curious as to why you consider DBGVIEW(*ALL) to be foolish.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Bob Cozzi
> Sent: Thursday, July 14, 2005 10:54 AM
> To: 'RPG programming on the AS400 / iSeries'
> Subject: RE: Regarding DBGVIEW(*STMT) in CRTBNRPG
> 
> 
> You probably could have gotten the answers to most of these questions
> yourself in less time than writing the message to the group 
> if you'd just
> started debug on a program...
> 
> DBGVIEW has a lot of options, but you use the ones you need. 
> If you don't
> want *STMT, don't use it. Most people use *SOURCE or *LIST, 
> some (foolishly
> in my view) use *ALL. 
> If DBGVIEW(*STMT) is used, then you can still debug but you 
> don't get to see
> the source, as you read in the documentation. This basically 
> allows you to
> continue to use the OPM debugger (sometimes called the 
> "system debugger") on
> RPGIV programs.
> 
> OPTION(*SRCSTMT) is preferred in RPG IV. It causes the 
> compiler to generate
> line numbers that typically match that of SEU. Since the 
> compilers were
> written by C programmers, they didn't really care about line 
> numbers for
> source code, so they wrote compilers that generated crazy 
> line numbering at
> compile time. A large number of RPG programmers complained, 
> and IBM added
> this option to solve the problem.
> 
> -Bob Cozzi
> www.RPGxTools.com
> If everything is under control, you are going too slow.
> - Mario Andretti
>