Db2

Db2

Connect with Db2, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only
  • 1.  DB2 Licenses for RTCL and odbc-cli

    Posted Fri July 14, 2023 04:53 PM

    Greetings,

    I have two problems regarding DB2 license.

    RTCL (Run-time Client)_License.

    I have a running installation. The license is 

    Product name:                     "IBM Data Server Client"
    Product identifier:               "db2client"
    Version information:              "11.1"

    I need to have another installation. But I could now find the original.

    The base installation package usually contains an valid license. Do you know exactly which package I need?

    The 2nd question is regarding odbc-cli installation connecting to mainframe.

    My understanding odbc-cli installation of odbc-cli is sepearate of the db2 engine installation, We have an aix machine that works fine.

    Now I wanted to make a Linux machine does the same. But it complains license failure.

    Is it the license for connecting to a mainframe is on the mainframe, which should enable the permission to allow this linux to connect?

    How do I activate license locally on this linux I read somewhere about db2connectactivate.sh but I could not find it anywhere.

    I saw licenses around  for db2consv_as.lic,  db2consv_ee.lic, db2consv.lic. Just don't know to activate it locally.

    Thanks for your help!

    --Kang



    ------------------------------
    Kang Sun
    ------------------------------


  • 2.  RE: DB2 Licenses for RTCL and odbc-cli

    Posted Sat July 15, 2023 08:42 AM
    Edited by Mark Barinstein Sat July 15, 2023 08:44 AM

    Hello,

    IBM Data Server Client and driver types don't require any licenses to work with Db2 for LUW databases.  
    You probably need a package which satisfies your application requirements. It's hard to tell which one you need exactly without these requirements. Refer the link above about their functionality.  
    All these client drivers/clients are available for download here.

    IBM licenses user connections from distributed (LUW) platforms to Db2 for Z/OS. This is why you need one of the Db2 Connect licenses either activated at Db2 for Z/OS subsystem or provided to the client.  
    If you want to register the corresponding license at Db2 for Z/OS, you may use the db2connectactivate utility.  
    If you want to register the corresponding license at your Db2 [Runtime] Client, you may use the db2licm utility with an `-a` option.  
    If you want to register the corresponding license at your IBM Data Server Driver for ODBC and CLI, you need to copy the corresponding license to its `installation_path/license` directory as described here



    ------------------------------
    Mark Barinstein
    ------------------------------



  • 3.  RE: DB2 Licenses for RTCL and odbc-cli

    Posted Thu July 27, 2023 04:44 PM

    Hi, thank you for the help.

    I eventually resolved the issue.

    Logically I have been thinking license has to be with the mainframe server. We somehow have to let the server grant the access permission to this RedHat box or this odbc driver.

    And indeed, we found db2connectactivate.sh inside a consv_azs package and with the correct server name, database name and access credentials, it worked.

    [license activator][7016][13472]Activation completed successfully for DB2 for IBM i version V7R1

    --Kang



    ------------------------------
    Kang Sun
    ------------------------------



  • 4.  RE: DB2 Licenses for RTCL and odbc-cli

    Posted Thu July 27, 2023 09:32 PM
    Edited by Youssef Sbai Idrissi Thu July 27, 2023 09:33 PM

    Regarding your DB2 license questions:

    1. RTCL (Run-time Client) License: If you need to have another installation of the IBM Data Server Client and you are missing the original installation package, you should reach out to IBM's support or sales team. They can provide you with the necessary installation package and ensure you have the appropriate license for your additional installation.

    2. ODBC-CLI Installation for Mainframe Connection: The ODBC-CLI installation is indeed separate from the DB2 engine installation. To connect to a mainframe, you will need a separate license called "DB2 Connect." This license is typically managed on the mainframe side, and it allows you to connect to DB2 on the mainframe from other platforms, such as Linux or AIX.

    To activate the DB2 Connect license locally on the Linux machine, you need to obtain the license file from the mainframe administrator or licensing team. The license file typically has a filename with the ".lic" extension, such as "db2consv_as.lic," "db2consv_ee.lic," or "db2consv.lic."

    Once you have the license file, you can activate it using the db2connectactivate command. The db2connectactivate.sh script is used on AIX systems, but on Linux, you can use the db2connectactivate command directly.

    Here's the command to activate the license:

    db2connectactivate <path_to_license_file>

    Replace <path_to_license_file> with the actual path to the DB2 Connect license file. After activating the license, you should be able to connect to the mainframe using ODBC-CLI from your Linux machine.

    Remember that licensing details can be specific to each organization, so it's essential to ensure you have the correct licenses for your specific use case and comply with any licensing agreements.



    ------------------------------
    Youssef Sbai Idrissi
    Software Engineer
    ------------------------------