This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dev:debug [2010/05/21 20:27] tdo |
dev:debug [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Debugging can be turned on in two ways: | Debugging can be turned on in two ways: | ||
| * Environment Variable | * Environment Variable | ||
| - | * SET command option | + | * SET statement from OdxSQL or from an ODBC or JDBC application |
| + | ===== Debugging with Operating System Environment Variables ===== | ||
| + | The OMNIDEX_DEBUG environment variable can be set on the server to aid in debugging an application. | ||
| - | ===== Debugging with Environment Variables ===== | + | * Server-only applications should turn on debugging prior to starting the application. |
| - | The OMNIDEX_DEBUG option environment variable can be set on the server to aid in debugging an application. | + | * Client-server applications should set this variable prior to starting the Omnidex Network Server listener that will be used by the client application. |
| - | Server-only applications should set turn on debugging prior to starting the application. | ||
| - | Client-server applications should set this variable prior to starting the Omnidex Network Server listener that will be used by the client application. | ||
| By default, the debugging information is output to a text file, odxdebug.log, located in the current working directory. The current working directory is the same location that the connected Omnidex environment file is located. | By default, the debugging information is output to a text file, odxdebug.log, located in the current working directory. The current working directory is the same location that the connected Omnidex environment file is located. | ||