Re: Do you compile production programs for debug?

At the latest release of the OS, I believe you can encrypt the debug information - so at least the source code is not easily looked at.

I like to use *ALL for debug - it adds almost nothing over the *LIST option - but *LIST is fine - if you use *SOURCE, you might get the wrong source or have none at all. What you get in the program object is a reference to the source member. The only option that adds materially to the program object is *LIST.

Now we DON"T have debug information in production (*STMT is the setting - pretty much the dog that doesn't hunt) - and I have it only if I specify it - others here don't use debug much to find issues.

Vern

On 3/31/2015 1:54 PM, (WalzCraft) Jerry Forss wrote:

Dean,

I was in banking for 18 years and was wondering if the original issue of not having debug was because of the IT auditors?
Sometimes they REALLY go out of their way to try and find something wrong.

I could see how the point was made.

That being said, being able to debug the actual production program without a recompile would be very beneficial.
It may have been compiled using an incorrect source member.
Just recompiling them does not guarantee the same object.

We always had production pgms with debug.

Jerry

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dean Eshleman
Sent: Tuesday, March 31, 2015 1:44 PM
To: Midrange-L Mailing list xxxx
Subject: Do you compile production programs for debug?

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
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com/>

______________________________________________________________________
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.
--
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.

Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change specifications without notice.

Confidentiality Notice:

This message and any attachments may contain confidential and privileged information that is protected by law. The information contained herein is transmitted for the sole use of the intended recipient(s) and should "only" pertain to "WalzCraft" company matters. If you are not the intended recipient or designated agent of the recipient of such information, you are hereby notified that any use, dissemination, copying or retention of this email or the information contained herein is strictly prohibited and may subject you to penalties under federal and/or state law. If you received this email in error, please notify the sender immediately and permanently delete this email. Thank You;

WalzCraft PO Box 1748 La Crosse, WI. 54602-1748
www.walzcraft.com Phone... 608-781-6355