Was this helpful?
Advanced Debugging
For advanced debugging, there are two additional variables that you can set for iimgmtsvr either in the environment or the Ingres symbol table:
II_TOOLS_LOGGING=level,X:\iitools_IT.log
This variable is set with the same values that can be used for II_GCA_LOG and II_GCA_TRACE (combined) or II_API_LOG and II_API_TRACE: 1–5, where 5 is the most verbose, followed by comma and the location for the trace file. A RAM disk or fast hard drive or flash drive is recommended for best performance, especially on Windows.
Example:
II_TOOLS_LOGGING=5,b:\iitools_IT.log
II_JNI_LOGGING=value,X:\iijni_IT.log
This variable has a set of values you may specify for the level. You may use either the mode word or the numeric value:
Mode
Value
Description
OFF
-1
No logging
TIMER
0
Used for timing of code
The following logging levels are those defined by the BSD syslog protocol (RFC3164).
EMERGENCY
1
System is unusable
ALERT
2
Action must be taken immediately
CRITICAL
3
Critical conditions
ERROR
4
Error conditions
WARNING
5
Warning conditions
NOTICE
6
Normal but significant conditions
INFO
7
Informational messages
DEBUG
8
Debug-level messages
TRACE
9
Almost everything that happens
Examples:
II_JNI_LOGGING=TRACE,b:\iijni_IT.log
II_JNI_LOGGING=4,f:\iijni_IT.log
More information:
Last modified date: 06/06/2024