Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 508
  • Last Modified:

MSAccess ODBC to Mainframe / Datacom SQL Statistics causes Datacom to crash

Dear experts.
I am connecting via a ODBC connection to a IBM Mainframe Datacom server.
Now the problem is, that the Datacom server is not the most recent version. Updating unfortunately is not an option.
Although a fix: RO40776 exists
Apparently some MSAccess SQL Statistics command, when querying the MainFrame DB via ODBC crashes the Datacom server.
ANY Idea how I can disable those MSAccess SQL Statistic commands?
Many thanks for your help
0
mruff
Asked:
mruff
  • 4
  • 2
1 Solution
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Apparently some MSAccess SQL Statistics command, when querying the MainFrame DB via ODBC crashes the Datacom server.
I'm not sure what "SQL Statistics commands" are, so I really can't help with that, but Access doesn't issue commands unless you instruct it, so there's nothing to "disable". You just wouldn't run the queries that crash the server.

If you could give more details of what you mean by "SQL Statistic commands" we might be able to help further.
0
 
mruffAuthor Commented:
Dear Scott,
no unfortunately not since I do not have access to this server and got the info from a colleague
What I did I double clicked on a linked table to view the data this lead to an odbc error (the error code was wrong, indicating I do not have access to the server, which was wrong since I can access the same server/same Db/same table via the same odbc without problems with winsql and do a select * from this table, which crashes the server when done from MSAccss)
probably the known DataCom Server fix RO40776  could help - did not have time to google it yet
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I double clicked on a linked table to view the data this lead to an odbc error (the error code was wrong, indicating I do not have access to the server, which was wrong since I can access the same server/same Db/same table via the same odbc without problems with winsql and do a select * from this table, which crashes the server when done from MSAccss)
May not be wrong, sincd WinSQL may be using a completely different driver.

If you create a NEW Access database, and create NEW links to the server, do you have the same issue?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
mruffAuthor Commented:
Yes a new DB has the same issue. Created empty DB with just one link table to the Mainframe DATACom table - does not work.
0
 
mruffAuthor Commented:
Dear Scott,
CA has provided us a potential fix. Once applied (next week) we can re test
0
 
mruffAuthor Commented:
finally upgrading the server part on the main frame solved the issue
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now