Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
In the latest versions of Qlik Sense, a native connector for IBM DB2 is included.
I have been unsuccessful in making it work.
The 50000 port does not work with DB2/400, but I haven't been able to figure out which port to use.
I would love to get rid of the OLEDB and ODBC drivers from client access as they are such a hassle.
Does anyone know if and how they can be used?
Or is this only for Universal DB2 (Linux, Windows, ...)
Rob?
Many thanks.
I've set up the connector with our V7R1 and it seems to work just fine ... (not as fast as the client access-driver though).
This documentation did help me... the port number in particular
IBM Test connect to DB2 AS/400 suing Data Direct ODBC Driver fails - United States
I also tried witouth success.
Anyway i found this information.
From here:
you can see that only the latest versions of DB2 are compatible: 10.5, 10.1, 9.5.
In client acces, from command line you can display the release version of DB2 with these command:
GO LICPGM.
option 10 - Display installed licensed programs.
hen the list of programs appears, press F11
And if you want to see the open port in AS400 you can use the command WRKSRVTBLE.
The current and latest release of IBM i is V7R3. DB2 has the same release version.
So it seems that this is only for UDB, or as it is now called DB2 LUW (Linux, Unix, Windows) - often pronounced 'DB2 love'.
Well, it looks like we're stuck with ODBC/OLEDB for a while longer...
I've set up the connector with our V7R1 and it seems to work just fine ... (not as fast as the client access-driver though).
This documentation did help me... the port number in particular
IBM Test connect to DB2 AS/400 suing Data Direct ODBC Driver fails - United States
What configuration did you use exactly?
I just followed the information in the document, and that showed me port 446.
The ping and telnet showed me it was reachable and open.
But configuring the IBM DB2 with the data connector that is included with Sense April 2018, using that specific port number ends up in time-out.
I tried both with and without explicitly naming the database.
wait up!
after repeatedly trying, it now works...
not sure if it will be very reliable though.
But saying it is slow, that is just being polite...
Although that may be related to how many resources the DRDA has been given access on the iSeries.