The Strategy ODBC Driver for DB2 Wire Protocol is shipped with Strategy product releases. This driver is manufactured by DataDirect Technologies. Refer to the Strategy product General Information Readme file for the precise version of the driver that is affiliated to a particular Strategy product release.
The Strategy DB2 Wire Protocol driver does not work properly unless packages exist on every DB2 server to which connection is intended. This driver can, however, create and bind these packages.
When connecting for the first time, the driver first checks if the packages already exist on the DB2 server. If the packages do not exist, the driver creates them automatically using the default values in the data source (DSN).
The User ID must have appropriate privileges for the driver to create and bind packages. These privileges are BINDADD for binding packages and GRANT for executing the packages. Also CREATEIN on the collection specified by the Package Collection option. These are typically the permissions of a Database Administrator (DBA). If the above User ID does not have these privileges, then a User ID with DBA privileges needs to create these packages by connecting with the driver. This connectivity with the latter User ID needs to be done just once, the very first time the driver attempts to connect to the DB2 server. Once the packages are created and bound, any other user should be able to connect to the database seamlessly.
Also, this package creation and binding can be done from either a Windows or Unix machine, using the corresponding Strategy DB2 Wire Protocol driver. It does not matter which machine it is done from – it has to be done just once, only the first time the database server is being accessed by this driver. After that any user can connect from any machine (Windows or Unix) to this database, as long as the created packages are accessible to public and the data source parameters do not change.
The initial driver connection to a particular DB2 server may take a few minutes because of the number and size of the packages that must be created on the server. Subsequent connections directly access the created packages and do not incur this delay.
As mentioned earlier, the DB2 Wire Protocol driver does this package creation and binding automatically. If the values in a data source change after the packages have been created, the user can re-create the packages manually with the new values. Refer to the following Knowledge Base technical note for details on how to manually create these packages:
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
