March 10, 2008 at 8:58 am
I have created a linked server to an IBM mainframe using the Microsoft OLE DB Provider for DB2, IBMDADB2. My connection works fine. However, I don't have access to the system catalog, SYSIBM. I have SYSADM rights on the DB2 instance and can see these tables in Reporting Services when I use the ODBC driver. Anyone have any ideas?
Thanks
March 10, 2008 at 9:35 pm
What is the error you are getting? It may have to do with naming convention. Using SQL "." notation versus IBM notation.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
March 11, 2008 at 9:31 am
I am not getting an error. I just don't have visibility or access to the SYSIBM catalog tables.
Thanks
March 27, 2008 at 9:44 am
jfauden
Just to make sure ... Does the user specified in the linked server has access to SYSIBM?
Check from the DB2 side... Can the user specified in the linked server access SYSIBM via IBM's iSeries Navigator?
Can you access any other tables/views/objects via your Linked Server connection?
We have a specific user for the linked server connection for cross-platform access.
If you can, give us more detailed information, and we should be able to help you muddle through.
Regards,
"Key"
MCITP: DBA, MCSE, MCTS: SQL 2005, OCP
March 27, 2008 at 10:35 am
Damon,
Can't explain it, but when I reconnected today, the userid now has visiblity to the SYSIBM catalog tables. Thanks for your advice, it prompted me to try again.
March 27, 2008 at 11:13 am
Well then, my "magic" touch seems to have manifested again!
Good to hear that you have the access you are expecting. It is also good to know that you have everything set up correctly!
Best Regards,
"Key"
MCITP: DBA, MCSE, MCTS: SQL 2005, OCP
March 27, 2008 at 11:51 am
Can't argue with that!
March 16, 2010 at 2:57 pm
jfauden
Hi there,
I have a question that gives me such a hard time,
I'm trying to connect to a mainframe COBOL Files from sql server 2000 or sql server 2008, I tried too many things and nothing worked,
CAn you explain to me how you done it????
Thanks
March 17, 2010 at 3:43 am
To access mainframe files, you will need an appropriate ODBC (or similar) driver. Google may help you find what is available, but I believe a company called NEON can provide what you need.
BTW, it makes no difference if the files are created using COBOL or any other mainframe language.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
July 12, 2010 at 3:29 pm
Using the NEON ODBC driver to access z/OS DB2 from the Linked Server, here's my problem:
Doing an Update, the Linked Server is interrogating the DB2 Catalog, looking for a Unique Index, I think. The result set from the Catalog is huge of course and it seems that once the Linked Server finds what he wants, he just move on and does not fetch all rows.
The Neon driver recognizes this and does a Cancel Result Set to avoid future cursor positioning problems. However, this Cancel also cancels the Update.
Is there a Linked Server configuration parm to fix this?
Dave
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply