Re: tbinit in debug mode?
David Williams wrote:
>
> In article <jlumbleyDxMLLz.Ip7@netcom.com>, Joe Lumbley
> <jlumbley@netcom.com> writes
> >zsun@br00dbss.med.osd.mil wrote:
> >
> >: Hi,
> >
> >: Has anyone heard of, or used tbinit in debug mode? I was told there was/is an
> >: un-documented option to run tbinit in debug mode, unfortunately the person who
> >
> >This is a good idea....Probably all of us have discovered a few undocumented
> >flags. Anybody interested in starting a thread to share some of this
> >arcane info? I'll start out with one I just discovered:
> >
> >export SQLIDEBUG=1:pathname/filename
> >
> ><insert the pathname/filename for a debug file>
> >
> >This generates a logfile of data that flows across I-Net. Haven't figured out
> >how to read the output yet....
> >
> >Joe
> >
> >
>
> I've discovered setting $AIOTRACE = 1 logs some AIO info to
> online.log.
>
> Still havn't discoever how to enable wait statistics (onstat -g wai)
> and queue statistics (for onstat -g qst). On my Online Tuning course
> the instructor just said they were undocumented. I've run strings
> on oninit as discovered QSTATS/WSTATS but can't seem to get them to
> work....
>
> Running strings on oninit brings up lots of things that must be either
> enviroment variables or onconfig settings but they are not
> documented...
>
> export AIO_TRACE=1; - outputs to online.log
>
> AFDEBUG
> AFTOMSGLOG
> AIOOP_OFFLINE
> AIOOP_READ
> AIOOP_WRITE
> ARCHIVE_TEST
> ASF_INIT_DATA
> ASF_INIT_PROCESS
> Auto reboot after abort.
> BTAPPENDERS
> CCFLAGS
> COMSPEC
> DBMAXPROC
> DBREMOTECMD
> DBVCLOSE
> DD_HASHMAX
> DD_HASHSIZE> DEAD
> DEBUG
> DEBUG_2PCFILE
> DELIMIDENT
> DOFF
> DR_TEST1
> DS_HASHSIZE
> DS_POOLSIZE> ENVIGNORE
> FAKE_SUBSYSTEM
> FASTIDXBLD
> FET_BUF_SIZE
> FORCE
> IFX_INPOLL_INTERVAL
> INFORMIXASFDBG
> INFORMIXCONRETRY
> INFORMIXCONTIME> INFORMIXNSF
> INFORMIXOPCACHE
> INFORMIXOPTDBj
> INFORMIXSQLHOSTS
> INFORMIXSTACKSIZEA
> IOSTATS
> IPSLEVEL
> IPSTRACE
> IXUSERS
> KAIOOFF=1
> KVLOCKING_TEST
> LA_BUFFER_LOCK
> LA_OFF
> LESS_MEMSRT
> LIGHT_SCANS
> LKNOTIFY
> LOCKDOWN
> LRUBUFFS
> LRUPOLICY
> LS_BUFFER_LOCK
> MUTEX_WAIT_LISTS
> NODEFDAC
> NON_M6_ATTRS_OK
> NOSHMSG
> NOSORTINDEX
> NO_TRAP_SIGNALS
> OPTOFC
> PC_HASHSIZE
> PC_POOLSIZE> PITSTOP
> PLOAD_CRASH_POINT
> PLOAD_CRASH_ROWS
> PLOAD_TRACE
> QPLANTEST
> QSTATS> REMCLIENT
> SINGLELEVEL
> SKALL
> SKCAPAB
> SKDEVICES
> SKINHIBIT
> SKPREVIEW
> SKSHOW
> SKTRACEFILE
> SORTTEMP
> SQDEBUG
> SQLIDEBUG = filename
> SQLPID
> STOP_RECOVERY
> TRACEFLAGS
> TRACES
> USER_TRACE
> USER_TRACEFLAGS
> WSTATS>
> anyone like to comment...things like "Auto reboot after abort.",
> KVLOCKING_TEST LRUPOLICY,FAKE_SUBSYSTEM,DR_TEST1,SQDEBUG and
> ARCHIVE_TEST sound interesting.
>
> PS don't try this on anything but a test system which can be
> destroyed.
>
> PPS Some of the above are documented - it's too late a night for
> me to remove them.
>
> --
> David Williams
Another one is if you are using DR and want to see what's going on
between servers set DR_TRACE=1 and pipe oninit to a file.