A Tale of Two Connections

You may also like...

5 Responses

  1. Andrej Furlanic says:

    For completeness, add “5. LDAP”, when DB2_ENABLE_LDAP enabled.
    Yes, even this is used rarely, that it would surprise most users.

  2. Dick Rietveld says:

    Wait a minute, let’s see if I get this right:

    After a fresh install there is an example db2cli.ini file. Contains rubbish so I usually throw it away and create a new one with the “db2 update cli” command.
    But then you’ve got the “db2cli” command which creates the db2dsdriver.cfg file for you? That’s new to me and a little bit confusing.
    That same “db2cli” command can also do the same as “catalog node & catalog database” and the “list db directory” command does not tell the whole story anymore….

    And this is all true when you do NOT use LDAP. LDAP is a complete new ballgame. The db2-luw-academy part 15 on youtube has a very nice demo how this all works on de database server. But how to use LDAP on the client…. I hope mr.db2-luw-academy reads this 🙂

    Usefull blog. My brain is shaken, not stirred.

  3. To salvage my shaken brain I did my own fiddling around with this new syntax and wrote my own blog: http://db2twilight.blogspot.nl/2014/04/another-look-at-db2-client.html
    Hope you like it

    • newbird says:

      Very helpful article, I tried it, the CLP does use the configuration inside db2dsdriver.cfg, but the configuration in db2cli.ini does not impact on CLP

  1. March 10, 2015

    […] a workaround for that too. You can find details on that in Ian’s guest blog post A Tale of Two Connections, or in his IDUG article on the same […]

Leave a Reply

Your email address will not be published. Required fields are marked *