[DEBUG]
debug_auxsql=0
debug_disk=0
debug_error=0
debug_ipc=0
debug_loader=0
debug_odbc=0
debug_sql=0
debug_version=0
debug_win1632=0
This section can be used to turn on diagnostics, by changing the values to 1, in various parts of DP4. The diagnostics are sent to the ERRLOG program. In some cases setting the value to 2, 3 or even 4, will produce additional diagnostics. Normally you will only turn on diagnostics when asked to do so by Itim Technology Solutions during problem diagnosis.
In 4.622 disk debug_disk=2 reports delays due to I/O. debug_disk=3 reports timings for all physical I/O. debug_disk=4 gives additional diagnostics showing how DP4 converted "logical" to "physical" I/O. In 4.620/4.621 debug_disk supports the same range of values, but the meanings are not so clearly defined. debug_disk=2 is intended not to impact performance too severely, and may well be of use if you are investigating performance. Some apparent delays are probably insignificant - the system clock usually has a granularity of 15ms, so delays around this length will occur from time simply because a clock interrupt has occurred while DP4 is doing I/O related work.
If these values are set to 1, DP4 programs will use up processor time formatting diagnostics even if load_errlog is set to 0.
debug_error and debug_version are set to 1 in the issued DP4 configuration file. Prior to release 4.620 the version information reported by debug_version often refers to one of the DLLs loaded by the program, and not the program itself. From release 4.620 version information is always accurate.