RE: RE: Regarding DBGVIEW(*STMT) in CRTBNRPG

Arco,

>I wonder why so much people want to keep debug information with their
programs that are moved to >production, so considered to be stable?...
If it is neccessary you can always create a new >"debugable" program
object isn't it? 

Perhaps their auditing requirements (as well as SOX, of course) require
that there is NO difference between production objects and development
objects. Even recompiling an object changes its date, and there's
nothing to stop it accidentally being changed when it is recompiled (for
instance, changed copybooks etc.). If you need to recompile the program
to debug it then by definition you're not debugging the same program out
in production. Chances are there are no differences, but you never know.

My only issue is that we rename our source modification libraries after
the object has rolled into production. So even though we compile with
DBGVIEW(*SOURCE) it may still show up as the source member not being
found when we try to debug a *PGM/*SRVPGM. And IBM didn't allow us to
specify a source member that is different from the one that was used to
build the module... I would really like the debugger to say "Specified
source member not avaialable - press F6 to choose a source member". We
could do this with ISDB, on the STRISDB command...

Rory