Debug parameters
Rob Berendt <[email protected]>
| Newsgroups | gmane.comp.systems.as400.domino |
|---|---|
| Message-ID | <OF3A3476CD.8C887BA7-ON852582E9.00481C4D-852582E9.0048818B@corp.dekko.com> |
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-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/domino400.