Using Datamaker with a DB2 Connect Remote Database

Document ID : KB000016297
Last Modified Date : 14/02/2018
Show Technical Document Details

How do I set up a DB2 Connect profile to allow Datamaker access the DB2 repository on another machine (or mainframe).  I can set up my ODBC32 sources,  but I am not able to get them to work with my DB2 database.   How do I configure my DB2 connectivity for Datamaker?


Typically the creation of a DB2 ODBC connection is out of scope for support and TDM,  but we've been able to create an ODBC configuration on a local machine to work with a remote DB2 database.  In this case,  here are the steps we used to establish the local alias.   For further details on the commands below,  please refer to IBM's website.


Before performing the steps,  make sure you have your IBM DB2 client is installed on your workstation,  since it will be the IBM DB2 Client that will create the local alias and ODBC connection.

Once you have the client installed,  here are the commands we used to build the ODBC connection:

>catalog tcpip node <YourNodeName> remote <yourhost> server <port number> 

>catalog db <your db> as <YOURALIAS> at node <YourNodeName> authentication dcs 

>connect to <YOURALIAS> user <yourid>   (you will then be prompted to supply your database password)

>bind 'C:\Program Files (x86)\IBM\SQLLIB\bnd\@ddcsmvs.lst' blocking all sqlerror continue grant public action add catalog system odbc data source <YOURALIAS> 

The bind step may fail that the bind already exists,  which you can safely ignore.

If you are able to verify your alias,  you will now be able to create your ODBC 32-bit sources.

Additional Information:

Above are the commands we have used to create the DB2 ODBC connection to a remote DB2 database on a mainframe.  If you need further assistance on setting up your ODBC connection, you should reach out to your DB2 administrator. There could be certain security or infrastructure settings that you will need to be aware of before setting up your local ODBC connection, where you may have to use a different set of commands for your environment (which is something the product support team won't be able to answer or advise on).