Forum Discussion

robarivas's avatar
robarivas
Post Patron
9 years ago

DB2 error: SQL0204N...is an undefined name

I'm trying to connect to an IBM DB2 database on z/OS using the IBM driver (the Microsoft driver requires a package collection to be specified whose value I am unaware of). If I select "Navigate using...
Need Help
robarivas's avatar
robarivas
Post Patron
9 years ago

Thanks again for the response Anonymous. That's great that you can successfully connect to DB2 for Windows. However, my issue is connecting to DB2 (using Power BI's built-in DB2 connector) on z/OS specifically. It seems like connecting to this kind of DB2 may be totally different. Is there anyway for Microsoft to test a connection to DB2 z/OS and let me know whether it works and, if so, what were the exact steps/configurations/etc. needed to make it work? 

 

Alternatively, are there any current Microsoft clients that are succefully connecting Power BI to DB2 z/OS that you can refer me to so that my IT department can reach out to them?

 

As for Data Studio, yes it was installed on the same machine I'm using for Power BI. Again, I'm not clear how Data Studio might help.

 

Thank you.

Anonymous's avatar
Anonymous
Not applicable
9 years ago

Hi robarivas,

I have no test enviorment for IBM on z/OS.

What is the error message do you get when choosing "Microsoft Driver" to connect to your database?

Thanks,
Lydia Zhang

  • robarivas's avatar
    robarivas
    Post Patron
    9 years ago

    Hello Anonymous. Below is the error message I receive using the Microsoft driver:

     

    Details: "Microsoft Db2 Client: The package corresponding to an SQL statement execution request was not found. SQLSTATE=51002 SQLCODE=-805"

    • Potsie's avatar
      Potsie
      New Member
      8 years ago

      Did you find a solution to this problem? I too am trying to connect to zOS DB2.

      • robarivas's avatar
        robarivas
        Post Patron
        8 years ago
        Hi Potsie
        My DBA team did something that made it so that I can connect using the Microsoft (not IBM) option. Unfortunately I don't know what they did differently to get the Microsoft option to work. It's also strange to me that the IBM option still doesn't work. Also, I've found that just connecting with ODBC seems to perform the same as far as I can tell.