Re: Regarding DBGVIEW(*STMT) in CRTBNRPG

so if you happen to get an error in a production run, you would be able
strsrvjob and the strdbg on the offending program and determine where the
program is by checking some variables so that you will know where to
restart, or how to recover from it, or allow it to continue and note any
manual fixes to the data may be needed without the need to kill the program.
this has saved me many times.  if you do not save the debug view, your only
option would be to dump the program.

----- Original Message ----- 
From: "Simonse, Arco (CMK)" <ArcoSimonse@xxxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, July 14, 2005 2:45 PM
Subject: 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.
>