Unlocking the UNIX/Linux Driver Manager with third-party drivers
- Last Updated: June 1, 2022
- 1 minute read
- DataDirect Connectors
- ODBC
- Documentation
If you are using third-party drivers, your application must unlock the Driver
Manager before the drivers can begin to use it. To unlock the Driver Manager, your application
can use either of the following methods.
- The application can use SQLSetConnectAttr to specify the license file and branding
password. For example:
rc = SQLSetConnectAttr (hdbc, 1041, "license_file"); rc = SQLSetConnectAttr (hdbc, 1042, "branding_password");SQLSetConnectAttr must be called after the connection handle is allocated and either before or immediately after connection.
- The application can issue the following statement to specify the license file and
branding password:
{license_file, branding_password}This statement must be issued immediately after connection.
where:
- license_file
- is the name of the driver license file. The license file takes the following forms,
where XX is the 2-character prefix you used to brand the files:
- IVXX.LIC (32-bit)
- DDXX.LIC (64-bit)
- branding_password
- is the password you specified when branding the drivers or Driver Manager. For more information, see "Branding the drivers on UNIX and Linux."
Note: Unlocking the Driver Manager with your application unlocks all of your third-party
drivers for the session. Progress drivers that you branded with the Driver Manager do not
need to unlock the Driver Manager.