RE: Regarding DBGVIEW(*STMT) in CRTBNRPG

I wonder why so much people want to keep debug information with their
programs that are moved to production, so considered to be stable?
Personally I always do DBGVIEW(*NONE) and OPTIMIZE(*FULL) when
applications are tested and approved.
If it is neccessary you can always create a new "debugable" program
object isn't it? 
Just curious.

Arco Simonse
pgmr

> -----Oorspronkelijk bericht-----
> Van: rpg400-l-bounces@xxxxxxxxxxxx 
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Namens Bob Cozzi
> Verzonden: donderdag 14 juli 2005 19:08
> Aan: 'RPG programming on the AS400 / iSeries'
> Onderwerp: RE: Regarding DBGVIEW(*STMT) in CRTBNRPG
> 
> It seems a bit lazy to me, not foolish. I mean why put all 
> that extra stuff into a program? I see people doing this 
> primarily because they're not sure which option to select. In 
> that case, I think it's foolish. *SOURCE, *LIST, or *COPY is 
> always the right choice. Programmers should pick the one that 
> they want to use most and change their compiler default to 
> that value. Then they only need to prompt for the change when 
> the other choice is desired.
> Putting *LIST into a program via *ALL when only *SOURCE is 
> needed, is overkill.
> Of course this opinion is based on 1995 technology--when IBM 
> was delivering the debugger with RPG IV. Back then we were 
> talking in terms of hundreds of megabyte drives. Today with 
> hundreds of gigabyte drives, perhaps space isn't an issue.  I 
> know I just installed a 100GB drive on my old ThinkPad. So 
> now my ThinkPad has approximately 3 times the storage of the 
> 400 that I use. I'd do the same to the 400 but I think I'd 
> rather make a down payment on a second home instead of adding 
> a few gig of dasd to my 400. <vbg> and <tic>
> 
> -Bob Cozzi
> www.RPGxTools.com
> If everything is under control, you are going too slow.
> - Mario Andretti
> 
> 
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx 
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Wilt, Charles
> Sent: Thursday, July 14, 2005 10:58 AM
> To: RPG programming on the AS400 / iSeries
> Subject: 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
> > 
> 
DISCLAIMER:
This message contains information that may be privileged or
confidential and is the property of C.Meijer B.V. It is intended only for the 
person to whom it is addressed. If you are not the intended recipient, you are 
not authorized to read, print, retain, copy,disseminate, distribute, or use 
this message or any part thereof. If you
receive this message in error, please notify the sender immediately and delete 
all copies of this message. 

This footnote also confirms that this email message has been swept by the 
presence of computer viruses