Re: Debug parameters

[Chris Whisonant <chris.whisonant@xxxxxxxxx>]

Yes, though I believe that the threadid one is always set on by default now.

---------------------------------------------------

Thanks,
Chris


On Tue, Aug 14, 2018 at 9:12 AM Rob Berendt <rob@xxxxxxxxx> wrote:

> If I cannot think of an open incident which may require these should I
> just remove these parameters mentioned in my log.nsf and console.log?
>
> NOTES.INI contains the following *DEBUG* parameters:
>  DEBUG_AMGR=*
>  DEBUG_CAPTURE=1
>  DEBUG_PANIC_ON_MARK_CORRUPT=1
>  DEBUG_SHOW_TIMEOUT=1
>  DEBUG_THREADID=1
>  DEBUG_TRAP_CORRUPTION=1
> Warning: Debug parameters could impact operation or performance.
> Contact your appropriate support vendor.
>
> I've already decided to remove
>  DEBUG_PANIC_ON_MARK_CORRUPT=1
> Which basically says "if I find a database marked for corruption then
> cause a panic on the server and bounce it.  Of course, it will notice the
> corruption again when the server restarts and does it's "Begin scan of
> databases to be consistency checked" and start another panic.  While it
> does a fantastic job of causing attention to fixing that database before
> corruption passes on to the rest of cluster members it vexes the users
> that the server is down, big time.
>
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Lotus Domino on the IBM i (AS/400 and iSeries) (Domino400)
> mailing list
> To post a message email: Domino400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/domino400
> or email: Domino400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/domino400.