DebugDialog

The DebugDialog appears when you select Debug from the Utilities PullDownMenu on
the Summary Screen or from any Overview Screen. The DebugDialog pertains to 
debugging Sun MTPScan itself, not to Sun MTP or CICS applications. You should only 
need to use the debug facility when trying to track down a problem with Sun MTPScan
in conjunction with Sun support personnel. The debug facility 
causes an enormous amount of processing overhead and is not recommended for use
in a production environment.

The Sun MTPScan DebugDialog unites the two DebugDialogs of kixScan4.0 into
a single Dialog. Unlike kixScan4.0, the DebugDialog is now always available from
its PullDownMenu location. The KIXSCANDEBUG is no longer required, and now
represents something completely different (see below). The Crash and Stop 
operations work the same as before: Crash produces a core dump (only useful when
running a debug version of Sun MTPScan) and Stop provides a breakpoint for a 
symbolic debugger. Each column of debug entries now has a button that either 
sets or unsets all of the toggles in that column. The KIXSCANDEBUG environment 
variable is now used to specify the name of a file in which to write debug 
output. If the KIXSCANDEBUG environment variable is not set, Sun MTPScan sends debug
output to stderr (to the xterm you invoked Sun MTPScan from). From within the 
DebugDialog, you may choose to send the debug output to stderr or to a file of 
your choice. Either key in the name of the file in the TextField and then select
the File RadioButton or snap the Filename button. The latter option produces a 
FileSelectionDialog that lets you visually choose the file. If the file already 
exists, Sun MTPScan asks you if you want to overwrite or append to the file.

See also: Dialog, ScrolledWindow, ToggleButton
