RE: Do you compile production programs for debug?

+1
Seriously, why wouldn't ya? Okay, maybe a little more memory/resources but,
honestly, I haven't worried/thought about THAT since S/3/34.

Jerry C. Adams
Revenge: The reason I get up each day.
IBM i Programmer/Analyst
--
NMM&D
615-832-2730


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Tuesday, March 31, 2015 1:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Do you compile production programs for debug?

Absolutely, we compile with debug. I am of the mindset that it should be
the IBM default for all of the compile commands. We have changed the
default value for all of the compile commands here.

- Dan

On Tue, Mar 31, 2015 at 2:44 PM, Dean Eshleman <Dean.Eshleman@xxxxxxxxxxxx>
wrote:

One of our developers asked why we don't compile our production
programs for debug. Their thought was, it would make it easier to
debug a production process when there was a problem. Currently, when
we have a production problem the developer tries to recreate it in a
test environment. If they can recreate it, they can debug it there.
In the rare circumstance they can't recreate it, we do recompile the
program for debug and put it into production. Currently, our
developers do not have authority to debug production jobs. A few
admin types have this authority, so it can be done.

Anyway, what do other people do. Do your production programs that you
write and use in house contain debug information? Are there any
negative side effects of doing that? Does it impact performance in
any way? TIA

Dean Eshleman

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.