3.1. OpenLink ODBC Driver for DB2 (Express Edition) for Mac OS X

3.1.1. Installation Guide

The OpenLink ODBC Driver for DB2 (Express Edition) is distributed as a Disk image (DMG) file. Simply double click on the disk image 'mul6edb2.dmg' to extract the installer mpkg file:

Figure 3.1. InstallerA_DB2.png

InstallerA_DB2.png

Double click on the mpkg file to run the installer and following the on screen instruction as indicated below to complete the installation:

Figure 3.2. InstallerB_DB2.png

InstallerB_DB2.png

Installer Welcome Dialog for the OpenLink ODBC Driver for DB2 (Express Edition):

Figure 3.3. Installer1_DB2.png

Installer1_DB2.png

Please review the readme file for installation requirements and known issues:

Figure 3.4. Installer2_DB2.png

Installer2_DB2.png

Please read the software license agreement before continuing your installation:

Figure 3.5. Installer3_DB2.png

Installer3_DB2.png

Select destination volume for driver installation:

Figure 3.6. Installer5_DB2.png

Installer5_DB2.png

Choose to perform a custom or default installation of the driver:

Figure 3.7. Installer6_DB2.png

Installer6_DB2.png

If you chose the custom option select which of the components below are to be installed:

Figure 3.8. InstallerC_DB2.png

InstallerC_DB2.png

The software must be installed as a user with administrative privileges on the machine:

Figure 3.9. Installer7_DB2.png

Installer7_DB2.png

After the driver has been installed you will be prompted for a license file. If a license file already exists on the machine then select the 'use exisiting file' option. A trial (try) or full (buy) license can be obtain by selecting the 'try and buy' option which loads our online try and buy web page:

Figure 3.10. Installer8_DB2.png

Installer8_DB2.png

To obtain the trial license you must be a registered user on the OpenLink Web site and login with the username (e-mail address) and password for that user. Click on the 'Shop' link to visit our online shop cart to purchases a full license if required:

Figure 3.11. InstallerD_DB2.png

InstallerD_DB2.png

Click on the 'download license' button to obtain the license file immediately and save to your desktop. Alternatively an auto e-mail will be sent to the registered users e-mail address with a link to their OpenLink Data Space (ODS) where all trial and full license files will be stored in the Briefcase for download at a later date.

Figure 3.12. InstallerE_DB2.png

InstallerE_DB2.png

Select the license file to be used for the installation:

Figure 3.13. Installer10_DB2.png

Installer10_DB2.png

Installation is complete:

Figure 3.14. Installer11_DB2.png

Installer11_DB2.png

3.1.2. Configuration

To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:

Figure 3.15. DSN0_AdminStart.png

DSN0_AdminStart.png

Click on the add button to Choose the ODBC Driver the DSN should be created for:

Figure 3.16. DSN1_AdminStart.png

DSN1_AdminStart.png

Choose the OpenLink DB2 Driver (Express Edition) v6.0 from the list of available drivers:

Figure 3.17. DSN3_SelectDB2Driver.png

DSN3_SelectDB2Driver.png

In the Data Source tab, select a suitable DSN name and optional description for the Data Source to be created:

Figure 3.18. DSN5_DB2Name.png

DSN5_DB2Name.png

The Connection Tab request the minimum paramters required to make a connection to the target database:

Figure 3.19. DSN7_DB2Host.png

DSN7_DB2Host.png

  • Host - the hostname of the server on which the DB2 database is running

  • Port - the TCP port on which DB2 listens

  • Database - a valid DB2 database alias

  • Username - the username of a valid DB2 user

  • Advanced - Additional optional configuration paramters:

Table 3.1. 

FullyMaterializeLobData Indicates whether the driver retrieves LOB locators for FETCH operations. The data type of this property is boolean. If the value is true, LOB data is fully materialized within the JDBC driver when a row is fetched. If this value is false, LOB data is streamed. The driver uses locators internally to retrieve LOB data in chunks on an as-needed basis It is highly recommended that you set this value to false when you retrieve LOBs that contain large amounts of data. The default is true.
ResultSetHoldability Specifies whether cursors remain open after a commit operation. Valid values are 1 - HOLD_CURSORS_OVER_COMMIT or 2 - CLOSE_CURSORS_AT_COMMIT.
CliSchema Specifies the schema of the DB/2 shadow catalog tables or views that are searched when an application invokes a DatabaseMetaData method.
CurrentSchema Specifies the default schema name that is used to qualify unqualified database objects in dynamically prepared SQL statements. This value of this property sets the value in the CURRENT SCHEMA special register on a server other than a DB2 UDB for z/OS server. Do not set this property for a DB2 UDB for z/OS server.
CurrentSQLID Specifies: The authorization ID that is used for authorization checking on dynamically prepared CREATE, GRANT, and REVOKE SQL statements. The owner of a table space, database, storage group, or synonym that is created by a dynamically issued CREATE statement. The implicit qualifier of all table, view, alias, and index names specified in dynamic SQL statements.
CurrentFunctionPath Specifies the SQL path that is used to resolve unqualified data type names and function names in SQL statements that are in JDBC programs. The data type of this property is String. For a DB2 UDB for Linux, UNIX and Windows server, the maximum length is 254 bytes. The value is a comma-separated list of schema names. Those names can be ordinary or delimited identifiers.
CurrentLockTimeout Directs DB2 UDB for Linux, UNIX and Windows servers to wait indefinitely for a lock or to wait for the specified number of seconds for a lock when the lock cannot be obtained immediately. The data type of this property is int. A value of zero means no wait. A value of -1 means to wait indefinitely. A positive integer indicates the number of seconds to wait for a lock.
JdbcCollection Specifies the collection ID for the packages that are used by an instance of the DB2 Universal JDBC Driver at run time. The data type of jdbcCollection is String. The default is NULLID.
CurrentPackageSet Specifies the collection ID to search for DB2 packages for the DB2 Universal JDBC Driver. The data type of this property is String. The default is NULLID. If currentPackageSet is set, its value overrides the value of jdbcCollection.
CurrentPackagePath Specifies a comma-separated list of collections on the server. The DB2 server searches these collections for the DB2 packages for the DB2 Universal JDBC Driver. The precedence rules for the currentPackagePath and currentPackageSet properties follow the precedence rules for the DB2 CURRENT PACKAGESET and CURRENT PACKAGE PATH special registers.
SecurityMechanism Specifies the DRDA security mechanism. Possible values are: 3 - User ID and password, 4 - User ID only, 7 - User ID, encrypted password,9 - Encrypted user ID and password, 11 - Kerberos. If this property is specified, the specified security mechanism is the only mechanism that is used. If the security mechanism is not supported by the connection, an exception is thrown.
KerberosServerPrincipal For a data source that uses Kerberos security, specifies the name that is used for the data source when it is registered with the Kerberos Key Distribution Center (KDC).
DeferPrepares Specifies whether to defer prepare operations until run time. The data type of this property is boolean.
ClientUser Specifies the current client user name for the connection. This information is for client accounting purposes. Unlike the connection user name, this value can change during a connection. For a DB2 UDB for Linux, UNIX and Windows server, the maximum length is 255 bytes.
ClientWorkstation Specifies the workstation name for the current client for the connection. This information is for client accounting purposes. This value can change during a connection. The data type of this property is String. For a DB2 UDB for Linux, UNIX and Windows server, the maximum length is 255 bytes.
ClientApplicationInformation Specifies application information for the current client for the connection. This information is for client accounting purposes. This value can change during a connection. The data type of this property is String. For a DB2 UDB for Linux, UNIX and Windows server, the maximum length is 255 bytes.
ClientAccountingInformation Specifies accounting information for the current client for the connection. This information is for client accounting purposes. This value can change during a connection. The data type of this property is String. For a DB2 UDB for Linux, UNIX and Windows server, the maximum length is 255 bytes.

As indiacted above the paramters of the options and preferences tabs are not required for a basic connection:

Figure 3.20. DSN10_DB2Options.png

DSN10_DB2Options.png

  • Row Buffer Size - This attribute specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.

  • Hide Login Dialog - Suppress the ODBC "Username" and "Password" login dialog box when interacting with your ODBC DSN from within an ODBC compliant application.

  • Read Only connection - Specify whether the connection is to be "Read-only". Make sure the checkbox is unchecked to request a "Read/Write" connection.

  • Drop Catalog from Meta calls - Enable this option to have the catalog name not appear for tables, views and procedures when requesting database meta-data.

  • Drop Schema from Meta calls - Enable this option to have the schema-name not appear for tables, views and procedures when requesting database meta-data.

  • SQLStatistics disabled - Check this box to have SQLStatistics() return an empty resultset. Use this if the underlying database does not support retrieving statistics about a table (e.g. what indexes there are on it).

  • No support of quoted identifier - If it is set, the call SQLGetInfo /bin/edit/Main/SQLGetInfo?topicparent=Main.UdaEeInstallConfigDB2 for 'SQL_IDENTIFIER_QUOTE_CHAR' will return the space (" "). It can be used if DBMS doesn't support quoted SQL like select * from "account"

  • No support of search string escape - If it is set, the call SQLGetInfo

    for 'SQL_LIKE_ESCAPE_CLAUSE' will return the space (" "). It can be used if DBMS doesn't support SQL escape patterns

  • Patch of NULL size of SQL_CHAR - If set this option overrides the size of SQL_CHAR column type returned by the database with the value set in the text box (in bytes). With the default value of 0 the driver uses the size returned by the database.

  • SQL_DBMS Name - Manually override the SQLGetInfo (SQL_DBMS_NAME) response returned by the driver. This is know to be required for products like Microsoft InfoPath for which the return the value should be "SQL Server".

Figure 3.21. DSN11_DB2Preferences.png

DSN11_DB2Preferences.png

  • Initialization SQL - Lets you specify a file containing SQL statements that will be run against the database upon connection, automatically.

  • Cursor Sensitivity - Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same - deleted rows don't appear in the rowset, updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the 'High Cursor Sensitivity' checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database.

  • MaxRows Override - Allows you to define a limit on the maximum number of rows to returned from a query. The default value of 0 means no limit.

  • Disable AutoCommit - Change the default commit behaviour of the OpenLink Lite Driver. The default mode is AutoCommit mode (box unchecked).

  • Disable Rowset Size Limit - Disable the limitation enforced by the cursor library. The limitation is enforced by default to prevent the Driver claiming all available memory in the event that a resultset is generated from an erroneous query is very large. The limit is normally never reached.

  • Defer fetching of long data - Defer fetching of LONG (BINARY, BLOB etc.) data unless explicitly requested in query. This provides significant performance increase when fields in query does not include LONG data fields.

  • Multiple Active Statements Emulation - Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver.

Click on the 'Test Data Source' button to make a connection to the database to verify connectivity:

Figure 3.22. DSN12_DB2Test.png

DSN12_DB2Test.png

Enter a vaild username and pasword for the database:

Figure 3.23. DSN13_DB2Login.png

DSN13_DB2Login.png

A successful connection to the database has been made:

Figure 3.24. DSN14_DB2Success.png

DSN14_DB2Success.png