Loading the Gateway ADC

Loading AUXWODBC

• Instructions for 16−bit DP4

  To load the ADC, ensure that SRVW is running, then run the ODBC gateway ADC program, AUXWODBC. The icon for SRVW will change to show that the ADC is running. After doing this, DP4 applications and utilities, such as BROWSER, are able to open any DP4 databases specified in the installation procedure and use the data on their associated ODBC data sources.

• Instructions for 32−bit DP4

  AUXWODBC is loaded like other ADCs, as described in the ADC developers manual. That is, in the [startup] section of the DP4 Configuration file include the following:

  [startup]
  1=dp4srvr.w32 −aux
  2=auxwodbc.w32

Please refer to the ADC developers' manual for instructions on loading multiple ADCs.

Loading AUXORACL

• Instructions for 32−bit Windows DP4

  AUXORACL is loaded like other ADCs, as described in the ADC developers manual. That is, in the [startup] section of the DP4 Configuration file include the following:

  [startup]
  1=dp4srvr.w32 −aux
  2=auxoracl.w32

• Instructions for Unix DP4

  AUXORACL is loaded like other ADCs, as described in the ADC developers manual.

  srv3 −aux −remain
  auxoracl −remain

Please refer to the ADC developers' manual for instructions on loading multiple ADCs. Prior to release 4.620/4.524 Options which are read from the DP4 Configuration file file in Windows DP4 are instead read from a file called AUXORACL.INI. This file must be in the /usr/datafit directory, and is identical in format to the DP4 Configuration file.

Diagnostics

The information in this section pertains to builds after 21st November 2001

You can obtain diagnostics from the Gateway ADC by setting debug_auxsql to a non zero value as follows:

• debug_auxsql=1 Prints diagnostics associated with call to a DP4 database function
• debug_auxsql=2 Additionally displays the name and value of each input field for executed SQL statements
• debug_auxsql=3 Additionally displays a hex dump for incoming and outgoing data

On Windows the diagnostics are only produced if error logging is turned on (e.g. by loading DP4 as follows:
srvw32 −start −load_errlog −debug_echo

On Unix the diagnostics are written to a file called auxoracl.out. This file is periodically restarted to prevent it growing too large and the previous file is renamed to auxoracl.out.bak. You can set the maximum size by using the −maxsize n command tail which specifies the maximum log file size in kilobytes, or you can prevent the file being restarted by specifying −maxsize 0 on the command line. The diagnostics are also echoed to screen if you specify −echo on the command line to auxoracl. To prevent auxoracl from detaching from the console specify −nodetach. You can force timing information to be added to the auxoracl.out file by specifying −timing.

Gateway ADCs and networking

If your SQL database does not reside on the same machine as the DP4 program there are two possoble configurations for accessing the database:

• Load the Gateway ADC on the client, and use the OEM database's native network client software to access the database.

• Load the Gateway ADC on the server underneath the DP4 network manager and access the database using DP4 networking. An example DP4 configuration on Windows would be as follows:

  [startup]
  1=dp4srvr.w32 -aux
  2=auxoracl.w32
  3=tcpmgr.w32

  The client machine loads DP4 networking in the normal way. It is probably a good idea to specify the −noblock command tail on the DP4 network requester, as it has been found that the "network block fetch optimisation" is counter-productive on OEM databases.

Which of these configurations you prefer should usually be a matter of informed choice (you should compare performance and total cost of ownership for the two configurations). In some cases there may be no suitable OEM network client available forcing you to use DP4 networking.