× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Two words (well TLA really)...

SOX
PCI

To satisfy the auditors, if you allow debugging on a production system
at all, it better take an act of God to enable it.

Charles

On Tue, Dec 14, 2010 at 2:46 PM, Aaron Bartell <aaronbartell@xxxxxxxxx> wrote:
As you know, finding problems by debugging live production environments is
a pretty bad technique to use regularly.

What exactly is bad technique about debugging live production environments -
especially since STRSRVJOB/STRDBG+IBMi OS make it so easy?  At the risk of
sounding like an un-refined coder, I debug in live production environments
first and foremost (vs. trying to recreate it), because that is often what
can get a customer back online the quickest.

Things like this are what gets lost in newer models of programming stacks,
IMO.  And it is also where tons of other tools are necessitated because of
the original issue not being addressed.

Aaron Bartell
www.MowYourLawn.com/blog
www.OpenRPGUI.com
www.SoftwareSavesLives.com



On Tue, Dec 14, 2010 at 9:49 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>wrote:

So does that mean I have to stop the server and restart it?  I wouldn't
think that is an acceptable practice in a production environment.

Unless they've changed something recently, servers typically run in debug
mode or not.  Debug mode allows you to attach a debugger and do your
thing, but it's not without some performance penalty.

The standard practice is to recreate the problem in a test environment in
debug mode.  As you know, finding problems by debugging live production
environments is a pretty bad technique to use regularly.  Sometimes it's
unavoidable, but it's not recommended.  The only time you do that is when
you can't recreate the problem.

In that case, you need to run your production environment in debug mode
until the problem occurs.  Then you can attach and debug.

Joe
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.