SQL Links - IBM DB2

Company

SQL LINKS DEVELOPER SUPPORT

SEARCH Borland Online/Developer Support

Tech Notes Index

IBM's CAE for NT/Win95 README.TXT
Search IBM's Software Library
Borland SQL Links 3.5 READLINK.TXT
Borland SQL Links 4.0 READLINK.TXT
32-bit DB2/BDE CLIENT CONFIG SQL Links 3.5 DB/2 driver PLEASE NOTE: DB2 ON WINDOWS 95 In Windows 95, you should catalog DB2 nodes using TCP/IP on the client, such as CATALOG TCP/IP NODE MYNODE ... If you use the Microsoft IPX/SPX protocol, the protocol will hang when metadata is retrieved. IBM reports that this is a Microsoft problem. The DB2 SQL Links driver can only access servers in the Windows 95 environment that are connected using TCP/IP. EXAMPLE CONFIGURATION OF IBM CAE CLIENT PC: (The steps below are examples only. Please consult your DB/2 server database administrator or IS department for specific information regarding the setup and configuration of your PC with the IBM CAE.) Quick Setup =========== If you have already configured you server and database node through the CAE Client Setup Utility and verified that the required CAE environment settings have taken effect (path, environment, etc.) then: 1)Run the BDECFG, 2)Add a DB2 alias for your DB/2 database NODE, 3)Save your changes 4)Verify a connection to DB2 server using the BDE ALIAS created in step 2 by: - Running the Database Desktop 7.0 (or above), run a BDE application that is database alias "aware" such as the Database Connection Checker (look for "32-Bit Utilities") to verify that the BDE can connect to your DB2 node. 32-BIT ONLY =========== - Run SETUP to install the IBM CAE (Client Application Enabler) for Win95/WinNT - Choose custom install. - Change the install directory to C:\DB232 (optional). - Restart WinNT / Win95 after installation. - Connection configuration: (2 methods) BE SURE TO FOLLOW THE WIN95 DIRECTIONS FOR WIN95 PLATFORM - MICROSOFT'S IPX/SPX PROTOCOL DOES NOT WORK PROPERLY FOR WIN95 (see note above). To connect to SERVERX server, configure the node and database as follows: METHOD #1 (preferred - using the Client Setup UI) FOR NT - - Launch the Client Setup utility from the IBM DB2 Group. If the DB2 Client Setup - Assistance screen appears, hit cancel. - Choose Node | New Name = serverx Protocol = IPX\SPX File Server = * (asterisk) Object Name = 00100f28.0020afc5e7af.879E (example object reference) - Highlight the SERVERX entry under the list of nodes. Choose Databases | Database | New Name = dbexamp Alias = s_dbexamp END (FOR NT) FOR WIN95 - - Edit the SERVICES file (C:\\SERVICES to add the lines db2v2port 3700/tcp db2v1port 3701/tcp (example service port entries) - Launch the Client Setup utility from the IBM DB2 Group. If the DB2 Client Setup - Assistance screen appears, hit cancel. - Choose Node | New Name = serverx Protocol = TCP/IP Hostname = serverx (you may need to use serverx's ip address-xxx.xxx.xx.xxx) Service Name = db2v2port (example service entry) - Highlight the SERVERX entry under the list of nodes. Choose Databases | Database | New Name = dbexamp Alias = s_dbexamp END (FOR WIN95) TEST CONNECTION FOR METHOD #1 Choose Test Database Connection. Enter username and password. You should see "Database connection validated successfully" Click OK NOTE: If you get an error message when using a TCP/IP connection which refers to a "gethostbyaddr" error, try changing the Hostname to serverx.mycompany.com (example host name) END (METHOD #1) METHOD # 2 (more painful - using the command line) - For Win95, edit the SERVICES file (C:\\SERVICES to add the lines db2v2port 3700/tcp db2v1port 3701/tcp (example host file and port entries) - Launch the DB2 Command Line processor (CLP) from the newly created IBM DB2 group. (Win95 - type "db2" at the command prompt when the CLP loads). For NT - db2>> Catalog IPXSPX node serverx remote * server 00100f28.0020afc5e7af.879E (example spx object name) For Win95 - db2>> Catalog tcpip node serverx remote xxx.xxx.xx.xxx server db2v2port (example ip address and port entry) (This tells the DB2 configuration directory where Serverx is). You will see "The CATALOG ... NODE command completed succesfully" db2>> Catalog database dbexamp as s_dbexamp at node serverx. (This tells DB2 that s_dbexamp is your alias for the dbexano database on Serverx. "s_dbexamp" is the value of the server name parameter when you set up your alias in the config file.) You will see "The CATALOG DATABASE command completed succesfully" db2>> quit c:\> exit TEST THE CONNECTION FOR METHOD #2 - Launch the DB2 CLP again. db2>> Connect to s_dbexamp user myusername using mypassword should see... Database product = DB2/2 2.1.1 SQL authorization ID = MYUSERNAME Local database alias = S_DBEXAMP END (METHOD #2) BDECFG - Add alias for s_dbexamp Verify BDE can connect to DB2 server - Run Database Desktop 7.0 (or above), run a BDE application that is database alias "aware" or run the Database Connection Checker (look for "32-Bit Utilities") to verify that the BDE can connect to your DB2 node.