Reportizer Documentation
Contents Index

Ways of Opening DB2 Databases

In Reportizer Opening Data Source dialog, there are several ways to open DB2 databases:

1. Opening through FD interface. Select FD interface, click DB2, then fill all needed database parameters.

2. Opening through ODBC DSN. Select ADO or BDE interface, then choose ODBC data source option and then select the needed ODBC DSN from the drop-down list. But first, you should create an ODBC DSN of the corresponding type using Windows administrative tools, and point it to the database.

3. Opening through BDE alias. Select BDE interface, then choose Alias option and then select the needed alias from the drop-down list. But first, you should create the alias of type DB2 using BDE Administrator tool and point it to the database.

4. Opening through connection string. Select ADO interface, then choose Connection string option and write a connection string. This way is very flexible and allows to specify many additional parameters in the connection string and override standard Reportizer connection behavior. It is recommended for advanced users. Here are basic connection strings (more examples and details can be found in the Internet):

Provider=DB2OLEDB;Network Transport Library=TCPIP;Network Address=xxx.xxx.xxx.xxx;Initial Catalog=MyCatalog;Package Collection=MyPkgCol;Default Schema=mySchema;User ID=myUsername;Password=myPassword;   (Microsoft OLE DB Provider for DB2 must be installed)

Provider=IBMDADB2;Database=myDatabase;Hostname=myServerAddress;Protocol=TCPIP;Port=50000;Uid=myUsername;Pwd=myPassword;   (IBM OLE DB Provider for DB2 must be installed)

Driver={IBM DB2 ODBC DRIVER};Database=myDbName;Hostname=myServerAddress;Port=myPortNum;Protocol=TCPIP;Uid=myUserName;Pwd=myPwd   (IBM DB2 Driver for ODBC must be installed)

DB2 client must be installed. The bit-version of it (32 or 64) must match the bit-version of the application.
When choosing the ODBC option, please make sure the corresponding ODBC driver installed and the bit-version of it matches the bit-version of the application (32 or 64).

See also

 Examples of ADO Connection Strings