Double-click the mpkg to start the installation process.

Figure3.72.OpenLinkUDA-4.5.dmg

You must have an Administration username and password to install the OpenLink Generic Multi-Tier Driver for ODBC. The Jaguar Installer will immediately prompt you to enter your Mac OS X Username and Password.

Figure3.73.Authentication

The installer will display a "Welcome" message. Click "Continue".

Figure3.74.Welcome

The next screen will display the Read-Me file, including any last-minute updates to these documents. Please read carefully, and click "Continue" when finished.

Figure3.75.Read Me

The next screen will display the License Agreement for the OpenLink Single-Tier Driver for ODBC. Please read, and click "Continue".

Figure3.76.Software License Agreement

You will be prompted to "Agree" to continue the installation, or "Diagree" to abort.

Figure3.77.Agree or Disagree to Licensing

You will be asked to select a Destination Volume. Generally, this should be your Mac OS X boot volume. Click on the desired disk icon, and then click "Continue".

Figure3.78.Choose Destination

You may now choose the Easy Install, or if you are an experienced user, you may Customize which components are installed. OpenLink generally recommends the Easy Install. If you have installed OpenLink or iODBC components in the past, click "Upgrade" to continue; otherwise, click "Install".

Figure3.79.Easy Install

Figure3.80.Custom Install

You will be shown a graphical progress bar as Installation progresses, followed by System Optimization.

Figure3.81.Installation Progress

When the process is complete, you will be told that the software was successfully installed. Click "Close" and your new database driver for ODBC is ready for use!

Figure3.82.Installation Proceeds

The OpenLink ODBC Administrator for Mac OS X currently supports creation of User and System Data Source Names (DSNs). Support for File DSNs will be delivered in a future release.

A User DSN is only available to the user who creates the data source. Its parameters are stored in that user's settings file ~/Library/Preferences/ODBC.preference.

A System DSN is available to the whole system so that any user, including the system itself, will be able to use that data source. Its parameters are stored in the System settings file /Library/Preferences/ODBC.preference.

A File DSN is a special 'mobile' data source that stores the data source information associated with the Driver in a file, which may then be copied and shared among different users and ODBC application host machines.

Any DSN can be tested for basic connectivity, to ensure that the basic parameters have been set correctly, through the OpenLink ODBC Administrator.

¶

iODBC Test.command (or /usr/bin/odbctest)

For more thorough testing, you can use iODBC Test, a sample application installed along with the OpenLink Generic Driver for ODBC. iODBC Test is a simple command-line, ODBC compliant, Interactive SQL client.

Either double-click the /Applications/iODBC/iODBC Test.command script or manually launch the Terminal application (found in /Applications/Utilities/).

Figure3.98.

If you used the script, you can skip ahead to the next paragraph; otherwise, ensure that the environment variables ODBCINI and ODBCINSTINI are set correctly and enter the command /usr/bin/odbctest.

At the prompt, type a question-mark (?) followed by the ENTER key, to show a list of available DSNs. Enter a connect string at the next prompt, using the syntax:

DSN=<DSN Name>[;UID=<username>[;PWD=<password>]]

Text enclosed in angle brackets < > should be replaced by your environment's specifics; text enclosed in square brackets [ ] is optional. The only mandatory parameter is the "DSN=". All other connect parameters may be set within the DSN itself. User authentication in the connect string will override similar information stored in the DSN. The following connect strings are all valid, assuming a DSN named test_dsn exists:

DSN=test_dsn
DSN=test_dsn;UID=;PWD=
DSN=test_dsn;UID=fred
DSN=test_dsn;UID=fred;PWD=
DSN=test_dsn;UID=fred;PWD=derf

A successful connection will cause display of the Driver's full version string, as it reports to any client application, followed by a SQL> prompt.

Enter ODBC connect string (? shows list, or DSN=...):
DSN=test_dsn;UID=fred;PWD=derf
Driver: 04.20.0402 OpenLink SQL Server Lite Driver
SQL>

Once the connection is made, any valid SQL query conforming to ODBC syntax (where applicable) may be executed. Use the command "quit" to close the connection.

If the query executes successfully you will see a table of the data returned by the query; if unsuccessful, you will see the entire error message returned from the back-end DBMS.

Use the command "quit" to close the connection. The prompt Again (y/n)? is asking whether you wish to connect to another DSN. Respond y(es) or n(o) and hit <return>. Yes brings you back to the Enter ODBC string prompt; no returns "Have a nice day".

SQL>quit
Again (y/n) ? n
Have a nice day.

From the Tracing Tab of the OpenLink ODBC Administrator, the level of Tracing can be configured.

Figure3.99.OpenLink ODBC Administrator, Tracing tab

When to trace. Use this option to turn tracing off or on. For a One-time only trace, the trace is made for the duration of the next connection. Click the Apply button to make your selection active. This option corresponds to the Trace and TraceAutoStop parameters in the preference files.

Custom trace library. Use the Select Library button to browse the machine for a library file that contains the code to intercept the trace output. This field should generally be left blank. When setting this parameter, you may use the Browse button to locate the library, or specify it manually. If specified manually, note that the location must be specified as it would be in a Terminal session. You may use ~/ as a shortcut to your user Home directory. This option corresponds to the TraceDLL parameter in the preference files.

Log file path. Specify the complete location of the file to which you wish to write the trace. You may use the Browse button to locate or create the file, or specify it manually. If specified manually, note that the location must be specified as it would be in a Terminal session. You may use ~/ as a shortcut to your user Home directory. This option corresponds to the TraceFile parameter in the preference files.

Trace Parameters in Preference Files. When the ODBC tracing parameters are changed, they are saved in the [ODBC] section of the ODBC.preference or odbc.ini file, whichever is active on your system.

The following example shows the settings for a one-time trace to a sql.log on the active user's Desktop.

[ODBC]
Trace         = 1
TraceAutoStop = 1
TraceDLL      =
TraceFile     = ~/Desktop/sql.log

Once the tracing of a connection is complete, the Trace and TraceAutoStop parameters will both be set to 0.

Trace. This parameter corresponds to the When to trace option in the Tracing tab. Set to 1, tracing is on; set to 0, tracing is off.

TraceAutoStop. This parameter corresponds to the One-time only option in the tracing tab. Set to 1, tracing will automatically stop after the next connection is closed; set to 0, tracing must be manually stopped. When tracing is automatically stopped, the Driver Manager will set both Trace and TraceAutoStop parameters to 0.

TraceDLL. This parameter corresponds to the Custom trace library option in the tracing tab. When setting this parameter, note that the file must be fully specified as it would be in a Terminal session. You may use ~/ as a shortcut to your user Home directory.

TraceFile

This parameter corresponds to the Log file path option in the tracing tab. When setting this parameter, note that the file must be fully specified as it would be in a Terminal session. You may use ~/ as a shortcut to your user Home directory.

As of iODBC 3.51.0, there are now more variables that may be included in the filename:

$P. This is the process-id (pid) of the application invoking the driver manager - allowing for per-process log-files

$U. This is the user-id under which the process is currently running

$T. This is the timestamp in YYYYMMDDHHmmSS format

$H. This is the home-directory of the user as whom the process is running

These options are case-insensitive. Hence you can specify

TraceFile=/tmp/iodbc-$U-$T-$P.log

if you wish.